Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b41facabead315eaf71bd24bee13c1dbd4b9d8bcd3a024cf8f4728071af08ba3

Tx prefix hash: aa6ab3c13d6764630d17322dff332272ce1e867f33b7ef701a6f8510f1790140
Tx public key: b52e26b4dabb1ae94772f4e1de4c1dbf9f4e18fad9a246d5d100aae64b9e2e46
Timestamp: 1717544085 Timestamp [UCT]: 2024-06-04 23:34:45 Age [y:d:h:m:s]: 00:207:18:06:56
Block: 1037200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148674 RingCT/type: yes/0
Extra: 01b52e26b4dabb1ae94772f4e1de4c1dbf9f4e18fad9a246d5d100aae64b9e2e4602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 009b6c081405ed016d501b92a5b2a987db8032fcb3a264f1bcaefbd55c868f3d 0.600000000000 1505731 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": 1037210, "vin": [ { "gen": { "height": 1037200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "009b6c081405ed016d501b92a5b2a987db8032fcb3a264f1bcaefbd55c868f3d" } } ], "extra": [ 1, 181, 46, 38, 180, 218, 187, 26, 233, 71, 114, 244, 225, 222, 76, 29, 191, 159, 78, 24, 250, 217, 162, 70, 213, 209, 0, 170, 230, 75, 158, 46, 70, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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