Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18a27508d95d1b0a3fdaf188f205047406081bf938227d9bf7099b35d71f82c8

Tx prefix hash: dff6c587fa635c771d6cbf3759e4afd0aa16a8eabf97091ee88d0fa73bf7a065
Tx public key: a6fd26653ac4c5d5517a8dfae86851a176187c10b322cc6c8d801f134b53e396
Timestamp: 1764278467 Timestamp [UCT]: 2025-11-27 21:21:07 Age [y:d:h:m:s]: 00:025:20:36:37
Block: 1421524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18503 RingCT/type: yes/0
Extra: 01a6fd26653ac4c5d5517a8dfae86851a176187c10b322cc6c8d801f134b53e3960211000000014e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bdd975f1f62bfa206ff12abccb3828cd60dfa2c0b8d268364c5c90de676e8a37 0.600000000000 1910081 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": 1421534, "vin": [ { "gen": { "height": 1421524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bdd975f1f62bfa206ff12abccb3828cd60dfa2c0b8d268364c5c90de676e8a37" } } ], "extra": [ 1, 166, 253, 38, 101, 58, 196, 197, 213, 81, 122, 141, 250, 232, 104, 81, 161, 118, 24, 124, 16, 179, 34, 204, 108, 141, 128, 31, 19, 75, 83, 227, 150, 2, 17, 0, 0, 0, 1, 78, 123, 252, 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