Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 261fac8d31e13ebc465b5efc8e0854efec219ce88cfdde0ab3f853ac7cd3f8b2

Tx prefix hash: 3448714feb2835e8456a4661197fbdc81b7083c98e3502a224ed7d5b0abd28cf
Tx public key: 1f6e0745f3296baeb16e0448cccc60d626b0e19aab2e0d9022ca231b718ee88f
Timestamp: 1723856582 Timestamp [UCT]: 2024-08-17 01:03:02 Age [y:d:h:m:s]: 00:303:00:21:44
Block: 1089532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216384 RingCT/type: yes/0
Extra: 011f6e0745f3296baeb16e0448cccc60d626b0e19aab2e0d9022ca231b718ee88f02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a142ffb0f3905a511b4769270c4c7c31ce52e12c8dde326efb9fd21f230992f5 0.600000000000 1564155 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": 1089542, "vin": [ { "gen": { "height": 1089532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a142ffb0f3905a511b4769270c4c7c31ce52e12c8dde326efb9fd21f230992f5" } } ], "extra": [ 1, 31, 110, 7, 69, 243, 41, 107, 174, 177, 110, 4, 72, 204, 204, 96, 214, 38, 176, 225, 154, 171, 46, 13, 144, 34, 202, 35, 27, 113, 142, 232, 143, 2, 17, 0, 0, 0, 10, 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