Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 554bf9ae4b9a0d7f2171f2b81811dd6988a6f6b7232913f8ea55aa77e73a0741

Tx prefix hash: 4902c1183ad2103853c83c5634985111a5179e776782e70639ff262643ad4b32
Tx public key: a23d2619fdb9e0b9f4c8023a162e20e245b494b01e1fb7fd3c5b454ee2624c62
Timestamp: 1737278927 Timestamp [UCT]: 2025-01-19 09:28:47 Age [y:d:h:m:s]: 00:150:04:31:59
Block: 1200623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107073 RingCT/type: yes/0
Extra: 01a23d2619fdb9e0b9f4c8023a162e20e245b494b01e1fb7fd3c5b454ee2624c620211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfb044818cac4fada9359f477eb396d4a9555c5a2b01d92eeb51dd694cc46a8d 0.600000000000 1687268 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": 1200633, "vin": [ { "gen": { "height": 1200623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfb044818cac4fada9359f477eb396d4a9555c5a2b01d92eeb51dd694cc46a8d" } } ], "extra": [ 1, 162, 61, 38, 25, 253, 185, 224, 185, 244, 200, 2, 58, 22, 46, 32, 226, 69, 180, 148, 176, 30, 31, 183, 253, 60, 91, 69, 78, 226, 98, 76, 98, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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