Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dff99d6e7fa53749ea6badddef004a0b61498433492ba33d9fb80f5e4592a3a9

Tx prefix hash: ce3320e00f7a15b549e2848773d33c3425bed3a81796267bbb447e0cc0dadfe4
Tx public key: bd906feb8fbeef3d9195f824fd10189b0553aab54c43f9acff818cf630b5f13c
Timestamp: 1725983470 Timestamp [UCT]: 2024-09-10 15:51:10 Age [y:d:h:m:s]: 00:280:05:38:51
Block: 1107166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200041 RingCT/type: yes/0
Extra: 01bd906feb8fbeef3d9195f824fd10189b0553aab54c43f9acff818cf630b5f13c02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da38f75add313b14f8d42365fdb8ca63601c4a3cb739504367d9b0784e0dd8e1 0.600000000000 1584773 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": 1107176, "vin": [ { "gen": { "height": 1107166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da38f75add313b14f8d42365fdb8ca63601c4a3cb739504367d9b0784e0dd8e1" } } ], "extra": [ 1, 189, 144, 111, 235, 143, 190, 239, 61, 145, 149, 248, 36, 253, 16, 24, 155, 5, 83, 170, 181, 76, 67, 249, 172, 255, 129, 140, 246, 48, 181, 241, 60, 2, 17, 0, 0, 0, 7, 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