Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abfd2ce4000857e779d77b6dcfe77dcc912c8f8304487316a12f5ef27004c518

Tx prefix hash: 672d3af41d98edca0b9823eb18d0a61da87608c0a16b560d66ef4719a6a6cee8
Tx public key: d84eb963b0d56c75607f33ae44c766a0fee48dc8f8b5db443436ce454910a03e
Timestamp: 1727444869 Timestamp [UCT]: 2024-09-27 13:47:49 Age [y:d:h:m:s]: 00:057:17:38:19
Block: 1119275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41260 RingCT/type: yes/0
Extra: 01d84eb963b0d56c75607f33ae44c766a0fee48dc8f8b5db443436ce454910a03e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 281cbedec5f8681d6ec5d8d9396bc399eb790e694df35e95ec503a98dc4d2945 0.600000000000 1600772 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": 1119285, "vin": [ { "gen": { "height": 1119275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "281cbedec5f8681d6ec5d8d9396bc399eb790e694df35e95ec503a98dc4d2945" } } ], "extra": [ 1, 216, 78, 185, 99, 176, 213, 108, 117, 96, 127, 51, 174, 68, 199, 102, 160, 254, 228, 141, 200, 248, 181, 219, 68, 52, 54, 206, 69, 73, 16, 160, 62, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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