Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b6fca07b2071ff83cb3821f1a1ea78b1c86a5283abc4da32f6e9e0098139cda

Tx prefix hash: 5e534913dc5fe74040cd9017d97237817fb38013c793f9a348805ac433c41c5a
Tx public key: fbe55d0a22069a3e1c45300052c5985e59568c961c5a8e09159c722d0fcc252b
Timestamp: 1707546358 Timestamp [UCT]: 2024-02-10 06:25:58 Age [y:d:h:m:s]: 01:059:05:14:38
Block: 954301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303382 RingCT/type: yes/0
Extra: 01fbe55d0a22069a3e1c45300052c5985e59568c961c5a8e09159c722d0fcc252b02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ffc4ee5c159c044af5f81b0254f7769620a0aebd3fa1aea73df8544b34ff5ad9 0.600000000000 1413581 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": 954311, "vin": [ { "gen": { "height": 954301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ffc4ee5c159c044af5f81b0254f7769620a0aebd3fa1aea73df8544b34ff5ad9" } } ], "extra": [ 1, 251, 229, 93, 10, 34, 6, 154, 62, 28, 69, 48, 0, 82, 197, 152, 94, 89, 86, 140, 150, 28, 90, 142, 9, 21, 156, 114, 45, 15, 204, 37, 43, 2, 17, 0, 0, 0, 1, 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