Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7b56e5c522556f654c7c8b862b1c5305ed26645ef58c8f7ab195f0eedea744

Tx prefix hash: 8c7d0365b50f33f7feaf9041a0b7be1b5aa5ab3fb05af6ceac7bafda772f96ed
Tx public key: bab8f0841b3030b47bdde98307dce3b72319f2f76a65d587ab41917bd1c79f46
Timestamp: 1673438262 Timestamp [UCT]: 2023-01-11 11:57:42 Age [y:d:h:m:s]: 01:363:19:39:53
Block: 672397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521055 RingCT/type: yes/0
Extra: 01bab8f0841b3030b47bdde98307dce3b72319f2f76a65d587ab41917bd1c79f460211000000038b7b6602000000000000000000

1 output(s) for total of 3.631362191000 dcy

stealth address amount amount idx
00: 5a3c7f6b4dc7e64161cac5f9e923ee8d13b4a6fff3aab9902420ced5857fba2a 3.631362191000 1113936 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": 672407, "vin": [ { "gen": { "height": 672397 } } ], "vout": [ { "amount": 3631362191, "target": { "key": "5a3c7f6b4dc7e64161cac5f9e923ee8d13b4a6fff3aab9902420ced5857fba2a" } } ], "extra": [ 1, 186, 184, 240, 132, 27, 48, 48, 180, 123, 221, 233, 131, 7, 220, 227, 183, 35, 25, 242, 247, 106, 101, 213, 135, 171, 65, 145, 123, 209, 199, 159, 70, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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