Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7b0c564e4c5f10d9eee2ad4347c29db263e8a81f6fcc4f5a776882ff1d05b84

Tx prefix hash: 8e7487cc68e7582fcf4a92829ea69b49746b398020681169d59a8c540fa7a3a1
Tx public key: 2e63a59093ef789acca4830e1a3e10a64c371353038ec82ac10aac3f5570de25
Timestamp: 1726599392 Timestamp [UCT]: 2024-09-17 18:56:32 Age [y:d:h:m:s]: 00:153:04:20:35
Block: 1112260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109257 RingCT/type: yes/0
Extra: 012e63a59093ef789acca4830e1a3e10a64c371353038ec82ac10aac3f5570de2502110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80f8cc64f0f9c359555d90f4b273f0f6391e214475ccec68d1b2ddde92fe3d9e 0.600000000000 1591519 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": 1112270, "vin": [ { "gen": { "height": 1112260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80f8cc64f0f9c359555d90f4b273f0f6391e214475ccec68d1b2ddde92fe3d9e" } } ], "extra": [ 1, 46, 99, 165, 144, 147, 239, 120, 154, 204, 164, 131, 14, 26, 62, 16, 166, 76, 55, 19, 83, 3, 142, 200, 42, 193, 10, 172, 63, 85, 112, 222, 37, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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