Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e1e86651fc699866797fec93e208348b2b04481f328b442b4f743d0381385b

Tx prefix hash: 0ab43fd405d2c76fc21dc312e63e6421064ca11d4a699c24d46c9a914241f768
Tx public key: 43c87a31261a9ef9f3cf49283d92b2da2300d5740bdd48f36c0d116d75a61784
Timestamp: 1704488886 Timestamp [UCT]: 2024-01-05 21:08:06 Age [y:d:h:m:s]: 01:050:07:28:00
Block: 928940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297038 RingCT/type: yes/0
Extra: 0143c87a31261a9ef9f3cf49283d92b2da2300d5740bdd48f36c0d116d75a61784021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb69621ae6a06a563ec0bf8d24a0982815e18b13e0b5ebe2f8a7f98f6096fd4b 0.600000000000 1386806 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": 928950, "vin": [ { "gen": { "height": 928940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb69621ae6a06a563ec0bf8d24a0982815e18b13e0b5ebe2f8a7f98f6096fd4b" } } ], "extra": [ 1, 67, 200, 122, 49, 38, 26, 158, 249, 243, 207, 73, 40, 61, 146, 178, 218, 35, 0, 213, 116, 11, 221, 72, 243, 108, 13, 17, 109, 117, 166, 23, 132, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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