Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb49417a8ef11ce4950423641b12bef07fe63d8e7876ec9a3fdbb7e4e4891f0a

Tx prefix hash: 77d3a228d738645c32458540bacd4e768df2aa1e67f9aed9cb3181375b148b73
Tx public key: 024a4fc161469556f5b88049e79f7683e77be821b47f483a3d49c7983d0900c5
Timestamp: 1736317835 Timestamp [UCT]: 2025-01-08 06:30:35 Age [y:d:h:m:s]: 00:302:18:41:29
Block: 1192702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213885 RingCT/type: yes/0
Extra: 01024a4fc161469556f5b88049e79f7683e77be821b47f483a3d49c7983d0900c502110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6660f8d2c2e973c1a05cc13ae5496c59e8b4806ef7e12e7cc11524aea999e29 0.600000000000 1679257 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": 1192712, "vin": [ { "gen": { "height": 1192702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6660f8d2c2e973c1a05cc13ae5496c59e8b4806ef7e12e7cc11524aea999e29" } } ], "extra": [ 1, 2, 74, 79, 193, 97, 70, 149, 86, 245, 184, 128, 73, 231, 159, 118, 131, 231, 123, 232, 33, 180, 127, 72, 58, 61, 73, 199, 152, 61, 9, 0, 197, 2, 17, 0, 0, 0, 15, 31, 10, 83, 235, 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