Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d78aa691b97fd009020b051f81a3f7c23abf182ed0d2cf19dda26d41f1f000

Tx prefix hash: 2da234a7bdd95b2b8f3957b37d3dd6f6cf291da81916ead33c3231a4c8ba1e04
Tx public key: 3d558317e9204147c9f704e3292fa5b5ad10438b35f5f666ad41e1af487f1acb
Timestamp: 1702345857 Timestamp [UCT]: 2023-12-12 01:50:57 Age [y:d:h:m:s]: 01:330:10:54:54
Block: 911195 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495011 RingCT/type: yes/0
Extra: 013d558317e9204147c9f704e3292fa5b5ad10438b35f5f666ad41e1af487f1acb02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e6af511aff303d609e5d6f7f40dfe74f86c2a93d9f1cf7c1203f2efb591dd21 0.600000000000 1368376 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": 911205, "vin": [ { "gen": { "height": 911195 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e6af511aff303d609e5d6f7f40dfe74f86c2a93d9f1cf7c1203f2efb591dd21" } } ], "extra": [ 1, 61, 85, 131, 23, 233, 32, 65, 71, 201, 247, 4, 227, 41, 47, 165, 181, 173, 16, 67, 139, 53, 245, 246, 102, 173, 65, 225, 175, 72, 127, 26, 203, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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