Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28837728242036b4e3e9c530d6a4c3d35209721ff7764c14f176a33064179549

Tx prefix hash: 8a34a9a2858770fe6325f404cff6f00f0fb0eb4d300be9dfb4b88aeb4eee1716
Tx public key: 1f54251f975a283ae14dce857174a4ecc6e6a3790ed8c40141c156ca91910561
Timestamp: 1722742031 Timestamp [UCT]: 2024-08-04 03:27:11 Age [y:d:h:m:s]: 00:081:10:58:30
Block: 1080292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58307 RingCT/type: yes/0
Extra: 011f54251f975a283ae14dce857174a4ecc6e6a3790ed8c40141c156ca9191056102110000000ee914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e0b9a012026c4df482d670abad82bc4c4ac1f2dc10a8ba643deb657864c32c7 0.600000000000 1553589 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": 1080302, "vin": [ { "gen": { "height": 1080292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e0b9a012026c4df482d670abad82bc4c4ac1f2dc10a8ba643deb657864c32c7" } } ], "extra": [ 1, 31, 84, 37, 31, 151, 90, 40, 58, 225, 77, 206, 133, 113, 116, 164, 236, 198, 230, 163, 121, 14, 216, 196, 1, 65, 193, 86, 202, 145, 145, 5, 97, 2, 17, 0, 0, 0, 14, 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