Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490286068c9c73f052dee8db9378dc99b3e31558245ba427758b71c2cc6d8514

Tx prefix hash: 9905c44281db3aae70eea9575dadaf89a38640e8b0d207d4ff5594cf9f9f6313
Tx public key: 4341c4e8ca6b21080d60231a108b7b314593bb48f17005211309f31aa5b91bd9
Timestamp: 1702265251 Timestamp [UCT]: 2023-12-11 03:27:31 Age [y:d:h:m:s]: 01:111:22:13:21
Block: 910523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341127 RingCT/type: yes/0
Extra: 014341c4e8ca6b21080d60231a108b7b314593bb48f17005211309f31aa5b91bd9021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af1689b69fca570f638c72d6eb0474b5e321ff8a14997d8b4c1db5662c8de06b 0.600000000000 1367684 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": 910533, "vin": [ { "gen": { "height": 910523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af1689b69fca570f638c72d6eb0474b5e321ff8a14997d8b4c1db5662c8de06b" } } ], "extra": [ 1, 67, 65, 196, 232, 202, 107, 33, 8, 13, 96, 35, 26, 16, 139, 123, 49, 69, 147, 187, 72, 241, 112, 5, 33, 19, 9, 243, 26, 165, 185, 27, 217, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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