Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933d2b74eb8af0a78c95a5aa09053e06d30b9bca809aea110aa0aea7728c767a

Tx prefix hash: 5b591e16aa85736ab378c6710f84dc315ed8c3fffe1bb73f728aa7423ba31dde
Tx public key: 0c6fb1dd06fd1a259027ce4d316ca3f663f62b73bd1cd5f54efe68e85c5d375f
Timestamp: 1702506600 Timestamp [UCT]: 2023-12-13 22:30:00 Age [y:d:h:m:s]: 01:155:03:26:19
Block: 912522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372047 RingCT/type: yes/0
Extra: 010c6fb1dd06fd1a259027ce4d316ca3f663f62b73bd1cd5f54efe68e85c5d375f02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37f204e1da842c70642aa18a877a1baf5ebe13702c7e977b2b9e6f483918b9de 0.600000000000 1369750 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": 912532, "vin": [ { "gen": { "height": 912522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37f204e1da842c70642aa18a877a1baf5ebe13702c7e977b2b9e6f483918b9de" } } ], "extra": [ 1, 12, 111, 177, 221, 6, 253, 26, 37, 144, 39, 206, 77, 49, 108, 163, 246, 99, 246, 43, 115, 189, 28, 213, 245, 78, 254, 104, 232, 92, 93, 55, 95, 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