Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0a0591a886341653a1235b5b64def3b746d1d0081e56f529443d77720fe52ec

Tx prefix hash: 034a0b93107aa2211d1d806292a846ed838747239d1b4da75054a62d1bed6d0a
Tx public key: c69e0ae9cf306affb235d86b559920bd92b3877c06bb3d063e12a2eed6d5c9a5
Timestamp: 1718818721 Timestamp [UCT]: 2024-06-19 17:38:41 Age [y:d:h:m:s]: 00:294:13:11:33
Block: 1047758 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210492 RingCT/type: yes/0
Extra: 01c69e0ae9cf306affb235d86b559920bd92b3877c06bb3d063e12a2eed6d5c9a502110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0c5e4dc309487178411c3838494648946e69d2bc9b0ccab0326cdd583977fb8 0.600000000000 1517665 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": 1047768, "vin": [ { "gen": { "height": 1047758 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0c5e4dc309487178411c3838494648946e69d2bc9b0ccab0326cdd583977fb8" } } ], "extra": [ 1, 198, 158, 10, 233, 207, 48, 106, 255, 178, 53, 216, 107, 85, 153, 32, 189, 146, 179, 135, 124, 6, 187, 61, 6, 62, 18, 162, 238, 214, 213, 201, 165, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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