Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bc0b16c907ed9e7f5273d17824272dbeae8fcf7daa5c56e4251001931ab1a45

Tx prefix hash: 6e454e13697963a3f236fb6c94180898b2327a383df47dbaddb71f13e35ad549
Tx public key: 55b07b1d690e5f5dfef4d1d5c2b1c7b097b9a0be1afb1ff187f79e5fc38c3852
Timestamp: 1700412245 Timestamp [UCT]: 2023-11-19 16:44:05 Age [y:d:h:m:s]: 01:176:07:05:18
Block: 895161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387202 RingCT/type: yes/0
Extra: 0155b07b1d690e5f5dfef4d1d5c2b1c7b097b9a0be1afb1ff187f79e5fc38c38520211000000024b8f5122000000000000000000

1 output(s) for total of 0.663681938000 dcy

stealth address amount amount idx
00: 9b450c0963a41876f912930fdcf791217b7ada6cea8a64304af61d52d04a4c63 0.663681938000 1351384 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": 895171, "vin": [ { "gen": { "height": 895161 } } ], "vout": [ { "amount": 663681938, "target": { "key": "9b450c0963a41876f912930fdcf791217b7ada6cea8a64304af61d52d04a4c63" } } ], "extra": [ 1, 85, 176, 123, 29, 105, 14, 95, 93, 254, 244, 209, 213, 194, 177, 199, 176, 151, 185, 160, 190, 26, 251, 31, 241, 135, 247, 158, 95, 195, 140, 56, 82, 2, 17, 0, 0, 0, 2, 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