Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5db3fcb54e5716d157e7f78cf7a6d24f37b74b5b8f58dda0e57ba4dee7d3c31

Tx prefix hash: fcfaa25861e37cf6ecb191b405cd6de2cb1140bc48481104132d7a258f6e69aa
Tx public key: e97e5ce76e81de7ea56dca06511c0590644c694c78daa3b12f08fa1d7bd9f0fd
Timestamp: 1697088428 Timestamp [UCT]: 2023-10-12 05:27:08 Age [y:d:h:m:s]: 01:092:07:33:17
Block: 867810 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327226 RingCT/type: yes/0
Extra: 01e97e5ce76e81de7ea56dca06511c0590644c694c78daa3b12f08fa1d7bd9f0fd021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.817683540000 dcy

stealth address amount amount idx
00: e8f76bed189ae2244ff10dae90512e17d498dd098bf60995813de9f058cd2962 0.817683540000 1322528 of 0

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": 867820, "vin": [ { "gen": { "height": 867810 } } ], "vout": [ { "amount": 817683540, "target": { "key": "e8f76bed189ae2244ff10dae90512e17d498dd098bf60995813de9f058cd2962" } } ], "extra": [ 1, 233, 126, 92, 231, 110, 129, 222, 126, 165, 109, 202, 6, 81, 28, 5, 144, 100, 76, 105, 76, 120, 218, 163, 177, 47, 8, 250, 29, 123, 217, 240, 253, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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