Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 398afbb36d77c61ecf7817052eb105b4bafaf9f47422df54ad93dd4907afe1a6

Tx prefix hash: 002ca9d4568c8049c38724df26550e15185e1f640389a4a0461b493de4c4df1a
Tx public key: 1073a5338f0d8df2beb4f85f24632b53c785e88f457631ca66197c5d8955f44f
Timestamp: 1613080902 Timestamp [UCT]: 2021-02-11 22:01:42 Age [y:d:h:m:s]: 04:024:03:58:07
Block: 196884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1036907 RingCT/type: yes/0
Extra: 011073a5338f0d8df2beb4f85f24632b53c785e88f457631ca66197c5d8955f44f02110000023627e2517e000000000000000000

1 output(s) for total of 136.660248239000 dcy

stealth address amount amount idx
00: 6dbbae1eb1e65e74e3bcdaf39e2594540adb453095411ba06642c3436b92e477 136.660248239000 402248 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": 196894, "vin": [ { "gen": { "height": 196884 } } ], "vout": [ { "amount": 136660248239, "target": { "key": "6dbbae1eb1e65e74e3bcdaf39e2594540adb453095411ba06642c3436b92e477" } } ], "extra": [ 1, 16, 115, 165, 51, 143, 13, 141, 242, 190, 180, 248, 95, 36, 99, 43, 83, 199, 133, 232, 143, 69, 118, 49, 202, 102, 25, 124, 93, 137, 85, 244, 79, 2, 17, 0, 0, 2, 54, 39, 226, 81, 126, 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