Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ee4fd485a45d22b2ccf7b2d5259bd2ecf2745f4ded570b46c87d1e62860944

Tx prefix hash: 337fe9441214a8a79de14d0bc24e80db66be5a8ea07fad35bbfa982056f1d758
Tx public key: 6b61b515dc0ca63e643b866198fc777f0126cc5f00c31f43b2640a9b1d4054a0
Timestamp: 1580700886 Timestamp [UCT]: 2020-02-03 03:34:46 Age [y:d:h:m:s]: 05:008:02:10:26
Block: 57623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1157681 RingCT/type: yes/0
Extra: 016b61b515dc0ca63e643b866198fc777f0126cc5f00c31f43b2640a9b1d4054a0021100000002391a8d0e000000000000000000

1 output(s) for total of 395.432082907000 dcy

stealth address amount amount idx
00: 08fefa004e1dfcfbfff9acef6a93d6e1480654bef6e4c525a8aa10fe6c9f1a4d 395.432082907000 106511 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": 57633, "vin": [ { "gen": { "height": 57623 } } ], "vout": [ { "amount": 395432082907, "target": { "key": "08fefa004e1dfcfbfff9acef6a93d6e1480654bef6e4c525a8aa10fe6c9f1a4d" } } ], "extra": [ 1, 107, 97, 181, 21, 220, 12, 166, 62, 100, 59, 134, 97, 152, 252, 119, 127, 1, 38, 204, 95, 0, 195, 31, 67, 178, 100, 10, 155, 29, 64, 84, 160, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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