Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e662f07a8ef591b38fb7d99c1bcc18dcab3105c949909fafc2e4af81631f2c81

Tx prefix hash: 3004b992ecf331ab5867c4e4ab81c62a005e20ae3dc8bc8d4dfdd3e830c82f62
Tx public key: 728becec6c6e9d6627d7699886d002c6f027ed48b91c3d99ea79ae01a7612a9e
Timestamp: 1723730902 Timestamp [UCT]: 2024-08-15 14:08:22 Age [y:d:h:m:s]: 01:082:10:29:16
Block: 1088489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317361 RingCT/type: yes/0
Extra: 01728becec6c6e9d6627d7699886d002c6f027ed48b91c3d99ea79ae01a7612a9e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf5198527999fab9d7409df56c11aed935a4a8604216d8aa8e934c7fbe672f26 0.600000000000 1563106 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": 1088499, "vin": [ { "gen": { "height": 1088489 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf5198527999fab9d7409df56c11aed935a4a8604216d8aa8e934c7fbe672f26" } } ], "extra": [ 1, 114, 139, 236, 236, 108, 110, 157, 102, 39, 215, 105, 152, 134, 208, 2, 198, 240, 39, 237, 72, 185, 28, 61, 153, 234, 121, 174, 1, 167, 97, 42, 158, 2, 17, 0, 0, 0, 2, 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