Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 998d8e1cb5a7f92cd9a227fab552da62df04b16b4288b382941d3c25d8dc3f83

Tx prefix hash: 7736362445bdda5b575004010592cee19ba007559831cfc313528099a7625753
Tx public key: fbc0d4d12682feb70409d1cf20c59e983337a8a5590d4b3da7c6e68098df0e89
Timestamp: 1728043476 Timestamp [UCT]: 2024-10-04 12:04:36 Age [y:d:h:m:s]: 00:206:01:54:16
Block: 1124246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147098 RingCT/type: yes/0
Extra: 01fbc0d4d12682feb70409d1cf20c59e983337a8a5590d4b3da7c6e68098df0e8902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fffa816b245ba039b3d1f95f8630bd6558765848e990691f6e9b34234113052c 0.600000000000 1606849 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": 1124256, "vin": [ { "gen": { "height": 1124246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fffa816b245ba039b3d1f95f8630bd6558765848e990691f6e9b34234113052c" } } ], "extra": [ 1, 251, 192, 212, 209, 38, 130, 254, 183, 4, 9, 209, 207, 32, 197, 158, 152, 51, 55, 168, 165, 89, 13, 75, 61, 167, 198, 230, 128, 152, 223, 14, 137, 2, 17, 0, 0, 0, 7, 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