Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce725394dc23e8cea37a280b8e37aa71e9d63922d3ec00580d61d87fe1604cd4

Tx prefix hash: bc5ecc5ac2947c4fb65172e00b26c880dc54f127dcb241c97b5ab55fce7715cf
Tx public key: cc4f9a2f1ac4debed2c1f7965dfab6930bd785f63c82127130427cd2b5b49c93
Timestamp: 1744125515 Timestamp [UCT]: 2025-04-08 15:18:35 Age [y:d:h:m:s]: 00:036:07:22:00
Block: 1257069 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25980 RingCT/type: yes/0
Extra: 01cc4f9a2f1ac4debed2c1f7965dfab6930bd785f63c82127130427cd2b5b49c93021100000006dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83e4b2300cda957b89e0a913a6c626e0e67a17ff9668babb569871fa5cf419d7 0.600000000000 1744188 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": 1257079, "vin": [ { "gen": { "height": 1257069 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83e4b2300cda957b89e0a913a6c626e0e67a17ff9668babb569871fa5cf419d7" } } ], "extra": [ 1, 204, 79, 154, 47, 26, 196, 222, 190, 210, 193, 247, 150, 93, 250, 182, 147, 11, 215, 133, 246, 60, 130, 18, 113, 48, 66, 124, 210, 181, 180, 156, 147, 2, 17, 0, 0, 0, 6, 219, 181, 113, 193, 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