Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95d2453b10acdf5ff83cafeb7a40041e74950e06915f07a53585204520e2497e

Tx prefix hash: ddbe1262e77c03f8c0cf3d16b86fe7ef1979fcb12f366b4cd64c6d49c4faed9c
Tx public key: cd88f2e5ac9223b5bcbbab3acdc4b45bb3ae0c52c99a1de9f228ff2b01fab891
Timestamp: 1733238336 Timestamp [UCT]: 2024-12-03 15:05:36 Age [y:d:h:m:s]: 00:200:15:30:55
Block: 1167211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143072 RingCT/type: yes/0
Extra: 01cd88f2e5ac9223b5bcbbab3acdc4b45bb3ae0c52c99a1de9f228ff2b01fab891021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a9bac4ceacdf57e23c6331a71f59e9e720edb1eb657b2ecf676fe90f85f3209 0.600000000000 1652906 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": 1167221, "vin": [ { "gen": { "height": 1167211 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a9bac4ceacdf57e23c6331a71f59e9e720edb1eb657b2ecf676fe90f85f3209" } } ], "extra": [ 1, 205, 136, 242, 229, 172, 146, 35, 181, 188, 187, 171, 58, 205, 196, 180, 91, 179, 174, 12, 82, 201, 154, 29, 233, 242, 40, 255, 43, 1, 250, 184, 145, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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