Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db275c0c45747b7bce90cb23a084ecbaa5b42d48536d2a71b39207b57b3fda47

Tx prefix hash: bc9d9b860eb13dc220ba96ba1608d105024059f5c12992a0bfacf9f8b2f8488e
Tx public key: f721529eabe64e194c0ff75b8a831c4a1b73ddb0cf85c4aeaa0d79a52ebb0bc2
Timestamp: 1726573677 Timestamp [UCT]: 2024-09-17 11:47:57 Age [y:d:h:m:s]: 00:195:07:57:58
Block: 1112053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139427 RingCT/type: yes/0
Extra: 01f721529eabe64e194c0ff75b8a831c4a1b73ddb0cf85c4aeaa0d79a52ebb0bc202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73f180fbe5bd11b71b333a828d8b38ecfce1e7aec3daaf9c5dcf7273d1ae5a7d 0.600000000000 1591236 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": 1112063, "vin": [ { "gen": { "height": 1112053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73f180fbe5bd11b71b333a828d8b38ecfce1e7aec3daaf9c5dcf7273d1ae5a7d" } } ], "extra": [ 1, 247, 33, 82, 158, 171, 230, 78, 25, 76, 15, 247, 91, 138, 131, 28, 74, 27, 115, 221, 176, 207, 133, 196, 174, 170, 13, 121, 165, 46, 187, 11, 194, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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