Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77f3a98f52e81b7a64c317a210ac2d9cb92a04e9f8def90bca6b1d10f8cf8cb6

Tx prefix hash: 514c3589cc4c7b11f93859e3bf1343bc266fe8348064f0a1e3b913a5a5bd3349
Tx public key: 802412f35151c0ce28bf9dc82542407b6d8097c74b5fa0fdb57109bd22d8a048
Timestamp: 1735187513 Timestamp [UCT]: 2024-12-26 04:31:53 Age [y:d:h:m:s]: 00:118:23:33:43
Block: 1183355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84827 RingCT/type: yes/0
Extra: 01802412f35151c0ce28bf9dc82542407b6d8097c74b5fa0fdb57109bd22d8a048021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc8649c914238221ca5f3943d9a01c6116b6dc1afb3b3aea7a86ad7c04206063 0.600000000000 1669800 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": 1183365, "vin": [ { "gen": { "height": 1183355 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc8649c914238221ca5f3943d9a01c6116b6dc1afb3b3aea7a86ad7c04206063" } } ], "extra": [ 1, 128, 36, 18, 243, 81, 81, 192, 206, 40, 191, 157, 200, 37, 66, 64, 123, 109, 128, 151, 199, 75, 95, 160, 253, 181, 113, 9, 189, 34, 216, 160, 72, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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