Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1b0467c89f40e7f1950158f2748c0383e0bfae57f19fc50776008efb22dffc0

Tx prefix hash: a5bef3b6308506cc0c99292139854e24af18f0ae7e9a34e817ffb98fc06f44c1
Tx public key: 5608ae1c602689d596516b8b63458d6c51bee3e6c7e0abc75ee984eaabf38479
Timestamp: 1659161901 Timestamp [UCT]: 2022-07-30 06:18:21 Age [y:d:h:m:s]: 02:256:16:36:05
Block: 554776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 704670 RingCT/type: yes/0
Extra: 015608ae1c602689d596516b8b63458d6c51bee3e6c7e0abc75ee984eaabf3847902110000000e6570b1ef000000000000000000

1 output(s) for total of 8.908343172000 dcy

stealth address amount amount idx
00: 5e2e4c287b7d9ed11925c18be3f9622b49f5206e9b6a2a8b7e3628d53e1bbba0 8.908343172000 986640 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": 554786, "vin": [ { "gen": { "height": 554776 } } ], "vout": [ { "amount": 8908343172, "target": { "key": "5e2e4c287b7d9ed11925c18be3f9622b49f5206e9b6a2a8b7e3628d53e1bbba0" } } ], "extra": [ 1, 86, 8, 174, 28, 96, 38, 137, 213, 150, 81, 107, 139, 99, 69, 141, 108, 81, 190, 227, 230, 199, 224, 171, 199, 94, 233, 132, 234, 171, 243, 132, 121, 2, 17, 0, 0, 0, 14, 101, 112, 177, 239, 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