Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 15aedb1c6faacf44846b5bc04cc2970c8c1e073bea1b271e6c4ae47290f13cb0

Tx prefix hash: b21af85d4c7ef5468fa0eef00d990f5d8b5657a44e79d560db99d70fada7df14
Tx public key: a1d2ac479aa024eb20b8f56caaf70b24bdc33af0d496a2e98caf60da23ece70b
Timestamp: 1734870816 Timestamp [UCT]: 2024-12-22 12:33:36 Age [y:d:h:m:s]: 00:101:06:22:15
Block: 1180751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72136 RingCT/type: yes/0
Extra: 01a1d2ac479aa024eb20b8f56caaf70b24bdc33af0d496a2e98caf60da23ece70b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc4df1dd67180b198afb55d3eac45550f8f5dd09716ed7fe3ee6167d63bd942f 0.600000000000 1667164 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1180761, "vin": [ { "gen": { "height": 1180751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc4df1dd67180b198afb55d3eac45550f8f5dd09716ed7fe3ee6167d63bd942f" } } ], "extra": [ 1, 161, 210, 172, 71, 154, 160, 36, 235, 32, 184, 245, 108, 170, 247, 11, 36, 189, 195, 58, 240, 212, 150, 162, 233, 140, 175, 96, 218, 35, 236, 231, 11, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8