Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2bba708faa6767548be668179846796e7350cae3200e5f0a87abb4f9bf84c88

Tx prefix hash: e47e9bd931c3868c3a1c495534a19c230f67275f767235d7cded4cb975d6a77e
Tx public key: cbe5f4a1c92db6d8ef70f0a6f044422709b70e4a1840f2316c9f0504f17bee7c
Timestamp: 1584772875 Timestamp [UCT]: 2020-03-21 06:41:15 Age [y:d:h:m:s]: 04:318:20:28:34
Block: 86413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123805 RingCT/type: yes/0
Extra: 01cbe5f4a1c92db6d8ef70f0a6f044422709b70e4a1840f2316c9f0504f17bee7c021100000001c2c2f844000000000000000000

1 output(s) for total of 317.452418301000 dcy

stealth address amount amount idx
00: 3e0f5cbff7d80800e9bb76f7f1eb20013a00fb97a5356ba5eab2f6fe2dc7106c 317.452418301000 155873 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": 86423, "vin": [ { "gen": { "height": 86413 } } ], "vout": [ { "amount": 317452418301, "target": { "key": "3e0f5cbff7d80800e9bb76f7f1eb20013a00fb97a5356ba5eab2f6fe2dc7106c" } } ], "extra": [ 1, 203, 229, 244, 161, 201, 45, 182, 216, 239, 112, 240, 166, 240, 68, 66, 39, 9, 183, 14, 74, 24, 64, 242, 49, 108, 159, 5, 4, 241, 123, 238, 124, 2, 17, 0, 0, 0, 1, 194, 194, 248, 68, 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