Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 607528c07141a60db2a0a42ba0c266d4fa3c0b121f2e54b98fb8806c01486827

Tx prefix hash: b71ae2c5b48a017fe0963518dc1bd344ac6eea4c2aa393919e2613ca6e23350c
Tx public key: fdb71d606b31f3044aa22a79924b02439c1fe4f9a5fb309059a41094dbeb332d
Timestamp: 1697467398 Timestamp [UCT]: 2023-10-16 14:43:18 Age [y:d:h:m:s]: 01:221:00:38:04
Block: 870950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419034 RingCT/type: yes/0
Extra: 01fdb71d606b31f3044aa22a79924b02439c1fe4f9a5fb309059a41094dbeb332d02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.798327569000 dcy

stealth address amount amount idx
00: 6f11e2c7c64af98a9af5ad4fbb8d91f40b6eb8ab5e9e7191e2a98d96bf8a011e 0.798327569000 1325913 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": 870960, "vin": [ { "gen": { "height": 870950 } } ], "vout": [ { "amount": 798327569, "target": { "key": "6f11e2c7c64af98a9af5ad4fbb8d91f40b6eb8ab5e9e7191e2a98d96bf8a011e" } } ], "extra": [ 1, 253, 183, 29, 96, 107, 49, 243, 4, 74, 162, 42, 121, 146, 75, 2, 67, 156, 31, 228, 249, 165, 251, 48, 144, 89, 164, 16, 148, 219, 235, 51, 45, 2, 17, 0, 0, 0, 4, 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