Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 574a4cb961eee7c24fc9b922f0bbf141eca1cd8bdd2dffa91d72321ffcfee793

Tx prefix hash: d48bcc4c67ca920f964aedfb387765f338fc6697fa690a3b0a2d05d39f07ee69
Tx public key: 7dec1dc6b4fe9b20af5e67324cea318c00b52f90962af535ec1cf075a4ac659c
Timestamp: 1716186332 Timestamp [UCT]: 2024-05-20 06:25:32 Age [y:d:h:m:s]: 00:334:01:41:21
Block: 1025941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238783 RingCT/type: yes/0
Extra: 017dec1dc6b4fe9b20af5e67324cea318c00b52f90962af535ec1cf075a4ac659c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90fda4d3fa9ae5ef703497d4ed648fabd3c81418483bab261042a4eb65ca8211 0.600000000000 1492750 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": 1025951, "vin": [ { "gen": { "height": 1025941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90fda4d3fa9ae5ef703497d4ed648fabd3c81418483bab261042a4eb65ca8211" } } ], "extra": [ 1, 125, 236, 29, 198, 180, 254, 155, 32, 175, 94, 103, 50, 76, 234, 49, 140, 0, 181, 47, 144, 150, 42, 245, 53, 236, 28, 240, 117, 164, 172, 101, 156, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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