Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 045637b55952585d4cdf32291ad08328f1da9af9cd779fb3f5069b49a7575db7

Tx prefix hash: ce64a617fdd409a368eb1dd1379cd5452bed1da7c590eb9b699173b457d2a68a
Tx public key: f2031c69306bcf176d5a031da4e8e0443a0d15dddc6065150e41c2440da79a3d
Timestamp: 1738572153 Timestamp [UCT]: 2025-02-03 08:42:33 Age [y:d:h:m:s]: 00:290:10:40:54
Block: 1211095 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205346 RingCT/type: yes/0
Extra: 01f2031c69306bcf176d5a031da4e8e0443a0d15dddc6065150e41c2440da79a3d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 343718b8ef4ba8e4f1551bf951c9fcfcf890956e42dd68a00e3a3494825d6d79 0.600000000000 1697854 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": 1211105, "vin": [ { "gen": { "height": 1211095 } } ], "vout": [ { "amount": 600000000, "target": { "key": "343718b8ef4ba8e4f1551bf951c9fcfcf890956e42dd68a00e3a3494825d6d79" } } ], "extra": [ 1, 242, 3, 28, 105, 48, 107, 207, 23, 109, 90, 3, 29, 164, 232, 224, 68, 58, 13, 21, 221, 220, 96, 101, 21, 14, 65, 194, 68, 13, 167, 154, 61, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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