Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 392d88adf4380fcc48686dd35531b7c647c1c4857510b96c625a8f56271b3084

Tx prefix hash: 34aebb422a54fc901746e7802a83fd132e783028bdd4239ad95fab649c94977b
Tx public key: 04ce5e1178539f3e4ae0ba76c5a7fae98e6ea929e5b08d08e1b2029d21fd62b8
Timestamp: 1762038260 Timestamp [UCT]: 2025-11-01 23:04:20 Age [y:d:h:m:s]: 00:008:01:19:13
Block: 1402954 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5766 RingCT/type: yes/0
Extra: 0104ce5e1178539f3e4ae0ba76c5a7fae98e6ea929e5b08d08e1b2029d21fd62b8021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bebfe9bd4298b1a35b09b30cb69c8c944bc355025efaf82ba175c6163245b20 0.600000000000 1891279 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": 1402964, "vin": [ { "gen": { "height": 1402954 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bebfe9bd4298b1a35b09b30cb69c8c944bc355025efaf82ba175c6163245b20" } } ], "extra": [ 1, 4, 206, 94, 17, 120, 83, 159, 62, 74, 224, 186, 118, 197, 167, 250, 233, 142, 110, 169, 41, 229, 176, 141, 8, 225, 178, 2, 157, 33, 253, 98, 184, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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