Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c67aaf8c37fed792faeee0f3d0647b005d9a4b5703c6512cf9534a9f08be4f3

Tx prefix hash: 7995cf68be9099733ad86c528fa72d007398193c5818cc91d5085b1753709440
Tx public key: a78fd9d82a00036c85c39169b5dd5f9c207c9e2419f8c04690dde73ac6397333
Timestamp: 1697280601 Timestamp [UCT]: 2023-10-14 10:50:01 Age [y:d:h:m:s]: 01:182:05:22:07
Block: 869408 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391275 RingCT/type: yes/0
Extra: 01a78fd9d82a00036c85c39169b5dd5f9c207c9e2419f8c04690dde73ac639733302110000000233af99f4000000000000000000

1 output(s) for total of 0.807775014000 dcy

stealth address amount amount idx
00: 2ae534e0609996bb1d8d2b53d684a652c9d0b2d5fabf3ce8a2495b3e28aecb22 0.807775014000 1324253 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": 869418, "vin": [ { "gen": { "height": 869408 } } ], "vout": [ { "amount": 807775014, "target": { "key": "2ae534e0609996bb1d8d2b53d684a652c9d0b2d5fabf3ce8a2495b3e28aecb22" } } ], "extra": [ 1, 167, 143, 217, 216, 42, 0, 3, 108, 133, 195, 145, 105, 181, 221, 95, 156, 32, 124, 158, 36, 25, 248, 192, 70, 144, 221, 231, 58, 198, 57, 115, 51, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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