Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8752714919336249d2dc6eefc9021ce706857f401a3babc10cb84b9ce5a3bfaf

Tx prefix hash: 99d41b8edc8d927fb0d2cabcc34d3b41931da9fbb013ee0adcc7fc4f9582fef9
Tx public key: d20ef1cff847f212862a603ea262c61a15ff206a40bce86e5e5aa58a5f29799e
Timestamp: 1751006249 Timestamp [UCT]: 2025-06-27 06:37:29 Age [y:d:h:m:s]: 00:145:07:31:04
Block: 1313694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101877 RingCT/type: yes/0
Extra: 01d20ef1cff847f212862a603ea262c61a15ff206a40bce86e5e5aa58a5f29799e021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2f0c243b527eee22653b9d0e1d8997b2f423aea3daa47e8303ce367abf2766c 0.600000000000 1801335 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": 1313704, "vin": [ { "gen": { "height": 1313694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2f0c243b527eee22653b9d0e1d8997b2f423aea3daa47e8303ce367abf2766c" } } ], "extra": [ 1, 210, 14, 241, 207, 248, 71, 242, 18, 134, 42, 96, 62, 162, 98, 198, 26, 21, 255, 32, 106, 64, 188, 232, 110, 94, 90, 165, 138, 95, 41, 121, 158, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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