Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044c7ce587d25732875692e76300ed8f72e0f5ed04d11945a42637cd738e2907

Tx prefix hash: 597ed273b2646f3e5a32ae7f2dee58674ed334ffc3feaa5b5bc0452a790f4100
Tx public key: a6511f0bd7baf983bd800ecd228ae86d90cb6aa5ca393c880ebb06ea3b9f9a5a
Timestamp: 1744676766 Timestamp [UCT]: 2025-04-15 00:26:06 Age [y:d:h:m:s]: 00:225:13:58:11
Block: 1261625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158966 RingCT/type: yes/0
Extra: 01a6511f0bd7baf983bd800ecd228ae86d90cb6aa5ca393c880ebb06ea3b9f9a5a021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b613a8c91b617f5cf90c4e058881c2ee77add9cf04ac8a348b3c013ead229365 0.600000000000 1748798 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": 1261635, "vin": [ { "gen": { "height": 1261625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b613a8c91b617f5cf90c4e058881c2ee77add9cf04ac8a348b3c013ead229365" } } ], "extra": [ 1, 166, 81, 31, 11, 215, 186, 249, 131, 189, 128, 14, 205, 34, 138, 232, 109, 144, 203, 106, 165, 202, 57, 60, 136, 14, 187, 6, 234, 59, 159, 154, 90, 2, 17, 0, 0, 0, 3, 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