Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3072855365701bb55ab5aeb5aea8989e9bb91f3135e5cd641a240be2622590fd

Tx prefix hash: 4c5016287cfc6caf28c82e5fb702e5d753b4613aebc9aead8656db8926399826
Tx public key: ea6dd16969ef3c3d9898bc9c7ca43d700a2f7ebe6fcdc4333a10019953e87e62
Timestamp: 1588737156 Timestamp [UCT]: 2020-05-06 03:52:36 Age [y:d:h:m:s]: 04:185:00:44:33
Block: 99089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1048470 RingCT/type: yes/0
Extra: 01ea6dd16969ef3c3d9898bc9c7ca43d700a2f7ebe6fcdc4333a10019953e87e6202110000000439be35fb000000000000000000

1 output(s) for total of 288.189247120000 dcy

stealth address amount amount idx
00: 1daee313c002d4e5ae91b0077a0f65db67d498970e7c4e267ef4af90938c025b 288.189247120000 174929 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": 99099, "vin": [ { "gen": { "height": 99089 } } ], "vout": [ { "amount": 288189247120, "target": { "key": "1daee313c002d4e5ae91b0077a0f65db67d498970e7c4e267ef4af90938c025b" } } ], "extra": [ 1, 234, 109, 209, 105, 105, 239, 60, 61, 152, 152, 188, 156, 124, 164, 61, 112, 10, 47, 126, 190, 111, 205, 196, 51, 58, 16, 1, 153, 83, 232, 126, 98, 2, 17, 0, 0, 0, 4, 57, 190, 53, 251, 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