Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453fa6e3b44730ec2c7b183a74aadc7c07c0f11142e7b584eba77d11179e58c5

Tx prefix hash: 962ae01bbfce77f0ca29c8e8252833d6201bd4c4f44f9530453af853d30ea4f9
Tx public key: 657f50f4eb8350eafb4b55c31b988ea98acd4e3209990957a70ffcea199c49ef
Timestamp: 1705211238 Timestamp [UCT]: 2024-01-14 05:47:18 Age [y:d:h:m:s]: 01:343:14:17:18
Block: 934926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504452 RingCT/type: yes/0
Extra: 01657f50f4eb8350eafb4b55c31b988ea98acd4e3209990957a70ffcea199c49ef02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2b42ad5b2fb1ce4568ba0701ca695db52a1b376d5db2394de206d5a2f5f523f 0.600000000000 1392942 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": 934936, "vin": [ { "gen": { "height": 934926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2b42ad5b2fb1ce4568ba0701ca695db52a1b376d5db2394de206d5a2f5f523f" } } ], "extra": [ 1, 101, 127, 80, 244, 235, 131, 80, 234, 251, 75, 85, 195, 27, 152, 142, 169, 138, 205, 78, 50, 9, 153, 9, 87, 167, 15, 252, 234, 25, 156, 73, 239, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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