Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1adf1b0fe78153a8664ded64596126a7f95f871e2ec77d279d8b8be2cf6ae550

Tx prefix hash: d090bb7dc7350551eaea541a1c117311233e4a568bfc11b5545bf6f551a87eaa
Tx public key: d6b51bb25301750155959a34ccf5dfca39c52c7def9ff8017c6a0ddded0b724e
Timestamp: 1725068918 Timestamp [UCT]: 2024-08-31 01:48:38 Age [y:d:h:m:s]: 00:291:00:23:20
Block: 1099576 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207777 RingCT/type: yes/0
Extra: 01d6b51bb25301750155959a34ccf5dfca39c52c7def9ff8017c6a0ddded0b724e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08f22c70c2b455f7ddd6c6cc8ab448be630fb9fde3e8569a835a543ef3238fa4 0.600000000000 1575541 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": 1099586, "vin": [ { "gen": { "height": 1099576 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08f22c70c2b455f7ddd6c6cc8ab448be630fb9fde3e8569a835a543ef3238fa4" } } ], "extra": [ 1, 214, 181, 27, 178, 83, 1, 117, 1, 85, 149, 154, 52, 204, 245, 223, 202, 57, 197, 44, 125, 239, 159, 248, 1, 124, 106, 13, 221, 237, 11, 114, 78, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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