Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a18e20c3fedf66aa79ed5a1f81590742d19497493d29cd4f7b57bb29b7d6467

Tx prefix hash: cf4bcf3ffc9962a791fbf7d993f9579cbbc320cf131e9c4efaf0776174ba6681
Tx public key: 7a0c76a31459d696ebdd6f499d0897a1288d0f0c5dc5e0eb64b3eb69cc19af1f
Timestamp: 1741509976 Timestamp [UCT]: 2025-03-09 08:46:16 Age [y:d:h:m:s]: 00:246:14:36:22
Block: 1235429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173974 RingCT/type: yes/0
Extra: 017a0c76a31459d696ebdd6f499d0897a1288d0f0c5dc5e0eb64b3eb69cc19af1f021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45c4d2ad7bbb60413809c6c9f2aa630e1ad7ae1b2310b7036a2e6e7e53ba7e63 0.600000000000 1722368 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": 1235439, "vin": [ { "gen": { "height": 1235429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45c4d2ad7bbb60413809c6c9f2aa630e1ad7ae1b2310b7036a2e6e7e53ba7e63" } } ], "extra": [ 1, 122, 12, 118, 163, 20, 89, 214, 150, 235, 221, 111, 73, 157, 8, 151, 161, 40, 141, 15, 12, 93, 197, 224, 235, 100, 179, 235, 105, 204, 25, 175, 31, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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