Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f4ded3a0a8ba5cb9ef5d291d91d31559404b4e1f1f036c8a9db77c97274968b

Tx prefix hash: dd621b6a7af88de89bb1295a7f7bae02bf11922f732587546020f589c6db4e9a
Tx public key: a1e89150c01c04c24ea4ed27ecbff3c366dd59cc2a8e7210d3d16046f463b984
Timestamp: 1643316898 Timestamp [UCT]: 2022-01-27 20:54:58 Age [y:d:h:m:s]: 03:278:02:53:30
Block: 426591 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 975674 RingCT/type: yes/0
Extra: 01a1e89150c01c04c24ea4ed27ecbff3c366dd59cc2a8e7210d3d16046f463b984021100000019db0c7f64000000000000000000

1 output(s) for total of 23.687937239000 dcy

stealth address amount amount idx
00: b00298dfd9d5bb30cc2c27e5dcf654e143c27506cde2938348ce37dfc75b44de 23.687937239000 835440 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": 426601, "vin": [ { "gen": { "height": 426591 } } ], "vout": [ { "amount": 23687937239, "target": { "key": "b00298dfd9d5bb30cc2c27e5dcf654e143c27506cde2938348ce37dfc75b44de" } } ], "extra": [ 1, 161, 232, 145, 80, 192, 28, 4, 194, 78, 164, 237, 39, 236, 191, 243, 195, 102, 221, 89, 204, 42, 142, 114, 16, 211, 209, 96, 70, 244, 99, 185, 132, 2, 17, 0, 0, 0, 25, 219, 12, 127, 100, 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