Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30fb09567ba4977f9ab64c14383d5bcfecf0bc7b199ba74e9c8528dcce9819f3

Tx prefix hash: 422c89aab43019e035ca32bd433cf8bf7fb471782add967137af1b2322c105f0
Tx public key: 817f71bc504e86c887f1210e56a8a1af9aaab7e7812fb5b9cc165c7b71ad4f71
Timestamp: 1739227739 Timestamp [UCT]: 2025-02-10 22:48:59 Age [y:d:h:m:s]: 00:329:20:43:51
Block: 1216527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233577 RingCT/type: yes/0
Extra: 01817f71bc504e86c887f1210e56a8a1af9aaab7e7812fb5b9cc165c7b71ad4f710211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b0ae187a97865d7d52585cfa01805724a9909e870f2a267548d692a50d8c5e1 0.600000000000 1703334 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": 1216537, "vin": [ { "gen": { "height": 1216527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b0ae187a97865d7d52585cfa01805724a9909e870f2a267548d692a50d8c5e1" } } ], "extra": [ 1, 129, 127, 113, 188, 80, 78, 134, 200, 135, 241, 33, 14, 86, 168, 161, 175, 154, 170, 183, 231, 129, 47, 181, 185, 204, 22, 92, 123, 113, 173, 79, 113, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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