Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e48c88ee0660f860b862f939aa8097847950444d5ea6ac869ec2818e60721f6

Tx prefix hash: b6cdd8fbd516bbc0e4361255533a977fbbe15061e7d1df18c5d1e4d0973b93bd
Tx public key: 8d50a5152ee0f7deee61518fb14023adae36e02b39c564da311e3a0814ae1742
Timestamp: 1734759214 Timestamp [UCT]: 2024-12-21 05:33:34 Age [y:d:h:m:s]: 00:090:18:01:16
Block: 1179829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64613 RingCT/type: yes/0
Extra: 018d50a5152ee0f7deee61518fb14023adae36e02b39c564da311e3a0814ae17420211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8f4b5b1db1bd1664ebec39bcd05e7aa216ddfbbeb4c17320e2a7e9bda1beba8 0.600000000000 1666228 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": 1179839, "vin": [ { "gen": { "height": 1179829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8f4b5b1db1bd1664ebec39bcd05e7aa216ddfbbeb4c17320e2a7e9bda1beba8" } } ], "extra": [ 1, 141, 80, 165, 21, 46, 224, 247, 222, 238, 97, 81, 143, 177, 64, 35, 173, 174, 54, 224, 43, 57, 197, 100, 218, 49, 30, 58, 8, 20, 174, 23, 66, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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