Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab041dc815933d02520834167d29d0a1528dc99210c1141f3ae4bb832dc60edc

Tx prefix hash: ca48dfea7c0badc1b64a12d77037d8590bb2f8374d0e9719ff513fdb89fff93f
Tx public key: 02364ad83804e4709f299e52b03f8131bbd14ebb45c66707ecf8d8dbf19c1b73
Timestamp: 1718200258 Timestamp [UCT]: 2024-06-12 13:50:58 Age [y:d:h:m:s]: 01:148:20:03:54
Block: 1042648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364926 RingCT/type: yes/0
Extra: 0102364ad83804e4709f299e52b03f8131bbd14ebb45c66707ecf8d8dbf19c1b730211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8444cc15a8497eef03e1e36c36fdfca5703c6f7783b548e09a5686a4e0df65e 0.600000000000 1511611 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": 1042658, "vin": [ { "gen": { "height": 1042648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8444cc15a8497eef03e1e36c36fdfca5703c6f7783b548e09a5686a4e0df65e" } } ], "extra": [ 1, 2, 54, 74, 216, 56, 4, 228, 112, 159, 41, 158, 82, 176, 63, 129, 49, 187, 209, 78, 187, 69, 198, 103, 7, 236, 248, 216, 219, 241, 156, 27, 115, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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