Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c7e6b4571dfcc54526ce8e24c70158b5dd3658ea3764e44ff549107b3f03a46

Tx prefix hash: d4a7d5e2bdf1493adf3e9c83254db4edea3538dadaae89b5f4ccda680dfea73b
Tx public key: f525f56b782d8bf1188a5162542401db1ef162fe3417f461fc2b8d1f630a8c2c
Timestamp: 1711663797 Timestamp [UCT]: 2024-03-28 22:09:57 Age [y:d:h:m:s]: 01:007:21:01:30
Block: 988463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266567 RingCT/type: yes/0
Extra: 01f525f56b782d8bf1188a5162542401db1ef162fe3417f461fc2b8d1f630a8c2c0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e24e5a3adff74a3b66dda66be8f3b0bdd2072d9e781636f4d4ec26b9a142f6e8 0.600000000000 1448742 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": 988473, "vin": [ { "gen": { "height": 988463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e24e5a3adff74a3b66dda66be8f3b0bdd2072d9e781636f4d4ec26b9a142f6e8" } } ], "extra": [ 1, 245, 37, 245, 107, 120, 45, 139, 241, 24, 138, 81, 98, 84, 36, 1, 219, 30, 241, 98, 254, 52, 23, 244, 97, 252, 43, 141, 31, 99, 10, 140, 44, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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