Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6edfb06b123f2c0c183583e3cbcccd5d93c8cb8db76b7f875cb2752c69aff0

Tx prefix hash: 58873ee9f8481c7df326f6b00bedcb4c791e19d7ee72a2ad0a0d74a331d178ac
Tx public key: 535d47e4b2e445dcd4ce652438e24fbaebca5dc73c95196e465ee0dc85ee2edf
Timestamp: 1711929685 Timestamp [UCT]: 2024-04-01 00:01:25 Age [y:d:h:m:s]: 01:227:20:38:58
Block: 990666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 421527 RingCT/type: yes/0
Extra: 01535d47e4b2e445dcd4ce652438e24fbaebca5dc73c95196e465ee0dc85ee2edf0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7f54d7a1aafe30fa5c7a3705763226d05c5f39a1019d647ad922a51964177ac 0.600000000000 1450990 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": 990676, "vin": [ { "gen": { "height": 990666 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7f54d7a1aafe30fa5c7a3705763226d05c5f39a1019d647ad922a51964177ac" } } ], "extra": [ 1, 83, 93, 71, 228, 178, 228, 69, 220, 212, 206, 101, 36, 56, 226, 79, 186, 235, 202, 93, 199, 60, 149, 25, 110, 70, 94, 224, 220, 133, 238, 46, 223, 2, 17, 0, 0, 0, 1, 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