Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4723ff351be3abd0f4df25da9ffd26e250133d5334048c78751b65770ebd8d93

Tx prefix hash: 3785694584768628c5e19eff572ad6f6d9f906bfed85e4b7002b8e3be47f2444
Tx public key: 0eae8d1f5643bff530f52b55c27a8aec466a544b92417189703093988f5caf5d
Timestamp: 1751817481 Timestamp [UCT]: 2025-07-06 15:58:01 Age [y:d:h:m:s]: 00:137:03:25:26
Block: 1320018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96423 RingCT/type: yes/0
Extra: 010eae8d1f5643bff530f52b55c27a8aec466a544b92417189703093988f5caf5d02110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4a309524eb3b730faf00e52d8a6cf20ac3da3d1f92ee4aa247230e0b3ef6e4b 0.600000000000 1807713 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": 1320028, "vin": [ { "gen": { "height": 1320018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4a309524eb3b730faf00e52d8a6cf20ac3da3d1f92ee4aa247230e0b3ef6e4b" } } ], "extra": [ 1, 14, 174, 141, 31, 86, 67, 191, 245, 48, 245, 43, 85, 194, 122, 138, 236, 70, 106, 84, 75, 146, 65, 113, 137, 112, 48, 147, 152, 143, 92, 175, 93, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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