Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d11dd630c8a61ac2132fd81d6a35e746bd6332d6919fb1030f5b164756b114bc

Tx prefix hash: d6f4d590730a507a1d60f8d698f5e4a9777aba9edeee27c27b8857f47f7fc55b
Tx public key: 0df31a1c6c90c541dc21746b6ed03a603fc4d2a3f61965cacd145ebb914e758f
Timestamp: 1717038216 Timestamp [UCT]: 2024-05-30 03:03:36 Age [y:d:h:m:s]: 00:316:05:41:19
Block: 1032996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226028 RingCT/type: yes/0
Extra: 010df31a1c6c90c541dc21746b6ed03a603fc4d2a3f61965cacd145ebb914e758f0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 780c27605ebf382dc7dae49ed7df7ed6ce6a5e18aa7d9a99e1d6c1ff860874db 0.600000000000 1501453 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": 1033006, "vin": [ { "gen": { "height": 1032996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "780c27605ebf382dc7dae49ed7df7ed6ce6a5e18aa7d9a99e1d6c1ff860874db" } } ], "extra": [ 1, 13, 243, 26, 28, 108, 144, 197, 65, 220, 33, 116, 107, 110, 208, 58, 96, 63, 196, 210, 163, 246, 25, 101, 202, 205, 20, 94, 187, 145, 78, 117, 143, 2, 17, 0, 0, 0, 2, 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