Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85930fb856ed18489bab6bf29055ce8e056a47c62e575dc13059d54f4b954c18

Tx prefix hash: 23679a256fe29a0c8359ab4dac614ce177e4a59e4c76dab8ab10fd23c5432e68
Tx public key: f67c20ce6b7af88ca81c44ebd70d9fdea5248756a20df90be76de6a7fdb81de3
Timestamp: 1764026834 Timestamp [UCT]: 2025-11-24 23:27:14 Age [y:d:h:m:s]: 00:003:07:47:42
Block: 1419441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2370 RingCT/type: yes/0
Extra: 01f67c20ce6b7af88ca81c44ebd70d9fdea5248756a20df90be76de6a7fdb81de3021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a7b3876c46bf2a3fee65ff5b8eb4643c83513db6f19250e8c0ef7dc85b006c 0.600000000000 1907978 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": 1419451, "vin": [ { "gen": { "height": 1419441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a7b3876c46bf2a3fee65ff5b8eb4643c83513db6f19250e8c0ef7dc85b006c" } } ], "extra": [ 1, 246, 124, 32, 206, 107, 122, 248, 140, 168, 28, 68, 235, 215, 13, 159, 222, 165, 36, 135, 86, 162, 13, 249, 11, 231, 109, 230, 167, 253, 184, 29, 227, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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