Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebb8fcb95efd8e48da4c94a725fae4e04379009d071e04b068f996cab456710d

Tx prefix hash: 20456d90912c84743f893c0408f2aefa0cba83a4bf958d87ef4f203355903137
Tx public key: 6d9a6c4684d22e768fcab2130a8fc039ece6f8da1b7cf015c7f783812008d09d
Timestamp: 1732432437 Timestamp [UCT]: 2024-11-24 07:13:57 Age [y:d:h:m:s]: 00:141:14:33:54
Block: 1160529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101022 RingCT/type: yes/0
Extra: 016d9a6c4684d22e768fcab2130a8fc039ece6f8da1b7cf015c7f783812008d09d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1835ed812ee41d50ad4e1fc4dc73d74689f4e4e489b574eb92f6aec7edfc549c 0.600000000000 1646176 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": 1160539, "vin": [ { "gen": { "height": 1160529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1835ed812ee41d50ad4e1fc4dc73d74689f4e4e489b574eb92f6aec7edfc549c" } } ], "extra": [ 1, 109, 154, 108, 70, 132, 210, 46, 118, 143, 202, 178, 19, 10, 143, 192, 57, 236, 230, 248, 218, 27, 124, 240, 21, 199, 247, 131, 129, 32, 8, 208, 157, 2, 17, 0, 0, 0, 2, 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