Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffa4abda83947624adc344c2dab7acdb43c96f204f052eb552ea8fd20e13296

Tx prefix hash: 1a4783cedcc547a49fd86a9ce5d0033495fa2951b557d1e6e6c0ac21011e0f6c
Tx public key: 01715c1740f9ecbd56d0b9db93925a9fccf35995a74bdb424f3e4ba8e690ea33
Timestamp: 1737852396 Timestamp [UCT]: 2025-01-26 00:46:36 Age [y:d:h:m:s]: 00:047:15:16:21
Block: 1205360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33872 RingCT/type: yes/0
Extra: 0101715c1740f9ecbd56d0b9db93925a9fccf35995a74bdb424f3e4ba8e690ea33021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a030f4a46cfec0999b51cb7a796eea19f47ed152fc8dc887316c97c26e08a713 0.600000000000 1692057 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": 1205370, "vin": [ { "gen": { "height": 1205360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a030f4a46cfec0999b51cb7a796eea19f47ed152fc8dc887316c97c26e08a713" } } ], "extra": [ 1, 1, 113, 92, 23, 64, 249, 236, 189, 86, 208, 185, 219, 147, 146, 90, 159, 204, 243, 89, 149, 167, 75, 219, 66, 79, 62, 75, 168, 230, 144, 234, 51, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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