Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b760abe520556fd74d0301ac931790b909e90f8fd36b6e76d90d48a9049b607

Tx prefix hash: bd63a5ceede9333bad6c4389120ad24e05c350b2db10f0b83da85790a00d3630
Tx public key: 668c9783d3b2f4611fc4664fafd7ca5c3ed03e53d19a7d24abfc6a0c35a38bc5
Timestamp: 1696588888 Timestamp [UCT]: 2023-10-06 10:41:28 Age [y:d:h:m:s]: 01:180:02:27:33
Block: 863667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389757 RingCT/type: yes/0
Extra: 01668c9783d3b2f4611fc4664fafd7ca5c3ed03e53d19a7d24abfc6a0c35a38bc50211000000074b8f5122000000000000000000

1 output(s) for total of 0.843942271000 dcy

stealth address amount amount idx
00: c72c319d1ce51a8de71c44f5c7f38da279edef03cd15752f72767fe333e5eebc 0.843942271000 1318141 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": 863677, "vin": [ { "gen": { "height": 863667 } } ], "vout": [ { "amount": 843942271, "target": { "key": "c72c319d1ce51a8de71c44f5c7f38da279edef03cd15752f72767fe333e5eebc" } } ], "extra": [ 1, 102, 140, 151, 131, 211, 178, 244, 97, 31, 196, 102, 79, 175, 215, 202, 92, 62, 208, 62, 83, 209, 154, 125, 36, 171, 252, 106, 12, 53, 163, 139, 197, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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