Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b487fc820b5ba89644807661bae67492ece66e912a75ca1fe9864a860bb9647

Tx prefix hash: a9d50bee79c8597b1b7dfa11439589da694275284233e8ee59341bc8a27c10be
Tx public key: c5ba229da5d64142813caf1a3ca12eebe1d0b933ceac62f3ffb1791bddf8eea4
Timestamp: 1704379565 Timestamp [UCT]: 2024-01-04 14:46:05 Age [y:d:h:m:s]: 02:030:00:10:38
Block: 928055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541069 RingCT/type: yes/0
Extra: 01c5ba229da5d64142813caf1a3ca12eebe1d0b933ceac62f3ffb1791bddf8eea4021100000005e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 937ed6f3d50e5ea7beab26933f0f66e4a0e9ce5dec86bbdf9f5a229ecb9c87eb 0.600000000000 1385911 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": 928065, "vin": [ { "gen": { "height": 928055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "937ed6f3d50e5ea7beab26933f0f66e4a0e9ce5dec86bbdf9f5a229ecb9c87eb" } } ], "extra": [ 1, 197, 186, 34, 157, 165, 214, 65, 66, 129, 60, 175, 26, 60, 161, 46, 235, 225, 208, 185, 51, 206, 172, 98, 243, 255, 177, 121, 27, 221, 248, 238, 164, 2, 17, 0, 0, 0, 5, 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