Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58c9a0b2b427c84acb60d182f6405f6a17d016a79389bd333dd87a423ead931e

Tx prefix hash: b0475adb9e0f6cd899aec5b4afce65973b6da51135b26adbc8097e737b2aa639
Tx public key: 9d3dac6c3abf072ce976271b338f59e4eda247364209b869f7ad5a861d228959
Timestamp: 1702138142 Timestamp [UCT]: 2023-12-09 16:09:02 Age [y:d:h:m:s]: 01:039:01:11:12
Block: 909477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289266 RingCT/type: yes/0
Extra: 019d3dac6c3abf072ce976271b338f59e4eda247364209b869f7ad5a861d22895902110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f744472fd52051048f7e489d9f06ff211822edfdb830dff6b8177b3e12c339a 0.600000000000 1366568 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": 909487, "vin": [ { "gen": { "height": 909477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f744472fd52051048f7e489d9f06ff211822edfdb830dff6b8177b3e12c339a" } } ], "extra": [ 1, 157, 61, 172, 108, 58, 191, 7, 44, 233, 118, 39, 27, 51, 143, 89, 228, 237, 162, 71, 54, 66, 9, 184, 105, 247, 173, 90, 134, 29, 34, 137, 89, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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