Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ea3ff1baf50364505401d2d57f3d66d73fa64fed605cde57e98c4de1e6ccbdf

Tx prefix hash: 6b6012f8edcac8e318aee5448968b7ddd2627c65b34a027a1125c39f6be578c8
Tx public key: cfcddf83e5aa98b492da8e2b9afa9ee8edacf1bcc614bfc7422614536d38f823
Timestamp: 1715984644 Timestamp [UCT]: 2024-05-17 22:24:04 Age [y:d:h:m:s]: 00:326:21:30:29
Block: 1024267 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233650 RingCT/type: yes/0
Extra: 01cfcddf83e5aa98b492da8e2b9afa9ee8edacf1bcc614bfc7422614536d38f823021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7d1221439ae787cd1ff5c514ce83f3a31b8b5009a4e0b05b7d3b9293054744f 0.600000000000 1489876 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": 1024277, "vin": [ { "gen": { "height": 1024267 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7d1221439ae787cd1ff5c514ce83f3a31b8b5009a4e0b05b7d3b9293054744f" } } ], "extra": [ 1, 207, 205, 223, 131, 229, 170, 152, 180, 146, 218, 142, 43, 154, 250, 158, 232, 237, 172, 241, 188, 198, 20, 191, 199, 66, 38, 20, 83, 109, 56, 248, 35, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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