Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357fed3ffd87fe15f3fb261621546d27ef2f18953405af712bf770b3f77bc538

Tx prefix hash: ec5f8ab6eca707eec6b5d9a745ff9099b1b4acd2ff2947f16fa40066eec37c8e
Tx public key: 71301f1255b532f957ee4cee790a278d65876f3e0d77b3adf1ef2952a190a7b0
Timestamp: 1685594348 Timestamp [UCT]: 2023-06-01 04:39:08 Age [y:d:h:m:s]: 01:226:03:03:21
Block: 772569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423026 RingCT/type: yes/0
Extra: 0171301f1255b532f957ee4cee790a278d65876f3e0d77b3adf1ef2952a190a7b002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.691057459000 dcy

stealth address amount amount idx
00: 75a0e5e481693a09b19fc0cf9db4fb1bd18b36ede3cdb4106308e8f2c848e9be 1.691057459000 1221982 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": 772579, "vin": [ { "gen": { "height": 772569 } } ], "vout": [ { "amount": 1691057459, "target": { "key": "75a0e5e481693a09b19fc0cf9db4fb1bd18b36ede3cdb4106308e8f2c848e9be" } } ], "extra": [ 1, 113, 48, 31, 18, 85, 181, 50, 249, 87, 238, 76, 238, 121, 10, 39, 141, 101, 135, 111, 62, 13, 119, 179, 173, 241, 239, 41, 82, 161, 144, 167, 176, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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