Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b024737407587d3bf2544b25b60e9f783a0b7915abda76a30ea7bf23c28ccb

Tx prefix hash: 28ca225c9351f52f372bfc71ed546fa7a5a9ad091c6eaac69ad0f9a87f472f9a
Tx public key: f8ac82a2a8f896e815fb5146e3c632a232bb37a988210b5fab06b7cf1161b657
Timestamp: 1673120443 Timestamp [UCT]: 2023-01-07 19:40:43 Age [y:d:h:m:s]: 02:124:18:48:42
Block: 669759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 610893 RingCT/type: yes/0
Extra: 01f8ac82a2a8f896e815fb5146e3c632a232bb37a988210b5fab06b7cf1161b65702110000000252542ceb000000000000000000

1 output(s) for total of 3.705188952000 dcy

stealth address amount amount idx
00: 0eae17f51c855d076c1b9608b15a021d88adf179fefad6ad150572b7aea64c00 3.705188952000 1111118 of 0

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": 669769, "vin": [ { "gen": { "height": 669759 } } ], "vout": [ { "amount": 3705188952, "target": { "key": "0eae17f51c855d076c1b9608b15a021d88adf179fefad6ad150572b7aea64c00" } } ], "extra": [ 1, 248, 172, 130, 162, 168, 248, 150, 232, 21, 251, 81, 70, 227, 198, 50, 162, 50, 187, 55, 169, 136, 33, 11, 95, 171, 6, 183, 207, 17, 97, 182, 87, 2, 17, 0, 0, 0, 2, 82, 84, 44, 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