Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c90dbb0852c746df62795ea992a616ffd7f6c3fcb2cb1580254354d066fb2515

Tx prefix hash: 44b772aac6981b877d2f5aa94d8a6b7c987956ce44f25b3b266ffb75557d9d1e
Tx public key: f6692f455078b98ccc84b14fdd11d16b881d5c4509889ed6ff95be5a7092ee4a
Timestamp: 1713165176 Timestamp [UCT]: 2024-04-15 07:12:56 Age [y:d:h:m:s]: 01:003:03:55:09
Block: 1000884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263218 RingCT/type: yes/0
Extra: 01f6692f455078b98ccc84b14fdd11d16b881d5c4509889ed6ff95be5a7092ee4a02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65c577e2d89ea29cf4ca5517e957ac516cd35bd4ba827dc264697408cda63368 0.600000000000 1461384 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": 1000894, "vin": [ { "gen": { "height": 1000884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65c577e2d89ea29cf4ca5517e957ac516cd35bd4ba827dc264697408cda63368" } } ], "extra": [ 1, 246, 105, 47, 69, 80, 120, 185, 140, 204, 132, 177, 79, 221, 17, 209, 107, 136, 29, 92, 69, 9, 136, 158, 214, 255, 149, 190, 90, 112, 146, 238, 74, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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