Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fced118d6c50e78322f4acf509449b1e1b0973790f0f9f7464b0c8df83cc501

Tx prefix hash: f427c2d08e3913c6b0235eb35c9055778393f5dc4dd7bbfa10e20b32a9d023f0
Tx public key: 888aac4aa96e1462e42cf78c8d352d06d619d201c66a160e6f7d0d0adf6cfc80
Timestamp: 1736826826 Timestamp [UCT]: 2025-01-14 03:53:46 Age [y:d:h:m:s]: 00:157:23:21:10
Block: 1196915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112566 RingCT/type: yes/0
Extra: 01888aac4aa96e1462e42cf78c8d352d06d619d201c66a160e6f7d0d0adf6cfc800211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec39f60faad2f3468cb2faa6d271089f3df06739e47c7630a46df5dcefe343cb 0.600000000000 1683520 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": 1196925, "vin": [ { "gen": { "height": 1196915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec39f60faad2f3468cb2faa6d271089f3df06739e47c7630a46df5dcefe343cb" } } ], "extra": [ 1, 136, 138, 172, 74, 169, 110, 20, 98, 228, 44, 247, 140, 141, 53, 45, 6, 214, 25, 210, 1, 198, 106, 22, 14, 111, 125, 13, 10, 223, 108, 252, 128, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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