Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a012a1b33778037a6aa04bc5143db1a201483f60cc33c7c4719b1677c703318

Tx prefix hash: 0e2640a71cefd7b4682fe6259837cbc48228d93f33b55290b844fa4dc8e4f155
Tx public key: 223eb6170c67019c2f2a7982d8f11966101db08840c4d584ac41d640e56cd82a
Timestamp: 1721918639 Timestamp [UCT]: 2024-07-25 14:43:59 Age [y:d:h:m:s]: 00:310:03:56:18
Block: 1073461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221630 RingCT/type: yes/0
Extra: 01223eb6170c67019c2f2a7982d8f11966101db08840c4d584ac41d640e56cd82a021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9233ea0643f1c87b3990f8e8d5c6b55964eb2ca9c12aa721f4adc09aa8dea9b0 0.600000000000 1545964 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": 1073471, "vin": [ { "gen": { "height": 1073461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9233ea0643f1c87b3990f8e8d5c6b55964eb2ca9c12aa721f4adc09aa8dea9b0" } } ], "extra": [ 1, 34, 62, 182, 23, 12, 103, 1, 156, 47, 42, 121, 130, 216, 241, 25, 102, 16, 29, 176, 136, 64, 196, 213, 132, 172, 65, 214, 64, 229, 108, 216, 42, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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