Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303a11b2e69adb462f9381f619ec8c121a307eeae74c561846dbf108354e432c

Tx prefix hash: e71c62980b1acd50fedb451a069f604abec1002f6b62efb50cc2a82c4fd0f0b0
Tx public key: b18554d76bc91449d0a9904cf3f08942e4abf4fc794ea5d7f081419a769c58dd
Timestamp: 1733956130 Timestamp [UCT]: 2024-12-11 22:28:50 Age [y:d:h:m:s]: 00:188:18:43:54
Block: 1173169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134623 RingCT/type: yes/0
Extra: 01b18554d76bc91449d0a9904cf3f08942e4abf4fc794ea5d7f081419a769c58dd0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6004ea74e0101e19b281e6556496dcc52ad67e17c690b622c50ecfa21be623b 0.600000000000 1659160 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": 1173179, "vin": [ { "gen": { "height": 1173169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6004ea74e0101e19b281e6556496dcc52ad67e17c690b622c50ecfa21be623b" } } ], "extra": [ 1, 177, 133, 84, 215, 107, 201, 20, 73, 208, 169, 144, 76, 243, 240, 137, 66, 228, 171, 244, 252, 121, 78, 165, 215, 240, 129, 65, 154, 118, 156, 88, 221, 2, 17, 0, 0, 0, 2, 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