Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cc8e0e1949603699c63fd174fd8f6246e31006d790ff573acfb21a5e50524c2

Tx prefix hash: 4a64e2aeaa3edee1567d165a3c7bb95c59d92c10ee1d16694ea7a78973adc319
Tx public key: 428c57960cbf3c6f915903af31bc6b4478d62951138392ca685623044d98914b
Timestamp: 1657244817 Timestamp [UCT]: 2022-07-08 01:46:57 Age [y:d:h:m:s]: 02:219:22:11:22
Block: 538996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 678284 RingCT/type: yes/0
Extra: 01428c57960cbf3c6f915903af31bc6b4478d62951138392ca685623044d98914b021100000003bf7ee4e7000000000000000000

1 output(s) for total of 10.048070014000 dcy

stealth address amount amount idx
00: b0686b36f9bdf7b8f47f006f18a3bfa937dc33bbdd41e1a03e5c437e018ff5f3 10.048070014000 969055 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": 539006, "vin": [ { "gen": { "height": 538996 } } ], "vout": [ { "amount": 10048070014, "target": { "key": "b0686b36f9bdf7b8f47f006f18a3bfa937dc33bbdd41e1a03e5c437e018ff5f3" } } ], "extra": [ 1, 66, 140, 87, 150, 12, 191, 60, 111, 145, 89, 3, 175, 49, 188, 107, 68, 120, 214, 41, 81, 19, 131, 146, 202, 104, 86, 35, 4, 77, 152, 145, 75, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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