Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 519182cefe6ca053dc419538f68ab3e043910d418049251d223758a064048ac2

Tx prefix hash: c7e6ee3e7ec9141507faf9e52a1acab8217dddcdbd01f4c550b0b2499a7c959e
Tx public key: 3138c40ff2899efc8c7fbfde311931b0ab9e1a2800743f0e924325dc25cbb7c2
Timestamp: 1721193292 Timestamp [UCT]: 2024-07-17 05:14:52 Age [y:d:h:m:s]: 00:323:13:44:57
Block: 1067466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231204 RingCT/type: yes/0
Extra: 013138c40ff2899efc8c7fbfde311931b0ab9e1a2800743f0e924325dc25cbb7c202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9810d81f48b593a731187f59910be2082a0591fd592f4a09c5b3ad07bfd95621 0.600000000000 1538283 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": 1067476, "vin": [ { "gen": { "height": 1067466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9810d81f48b593a731187f59910be2082a0591fd592f4a09c5b3ad07bfd95621" } } ], "extra": [ 1, 49, 56, 196, 15, 242, 137, 158, 252, 140, 127, 191, 222, 49, 25, 49, 176, 171, 158, 26, 40, 0, 116, 63, 14, 146, 67, 37, 220, 37, 203, 183, 194, 2, 17, 0, 0, 0, 8, 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