Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b49df88cc96d1620ed4e92171897cdcc7fd00a1f1bcecd91aa3d09dce7fb8dcf

Tx prefix hash: d597f9976256641651635a2067714e9436f99aad0b65be2d6e3b3928d4e7d41d
Tx public key: d70e6fb79245473f88e12f44ccca806d66f5a43ad1d6809ef5f86d0a1e93f09d
Timestamp: 1649668015 Timestamp [UCT]: 2022-04-11 09:06:55 Age [y:d:h:m:s]: 03:203:23:30:39
Block: 477859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 923954 RingCT/type: yes/0
Extra: 01d70e6fb79245473f88e12f44ccca806d66f5a43ad1d6809ef5f86d0a1e93f09d021100000001d3fcec30000000000000000000

1 output(s) for total of 16.019722996000 dcy

stealth address amount amount idx
00: 3f864e1d2ad4b402aef66abc2d3e5df66b5ad4464746d3cf5fb0f71ca6a207d7 16.019722996000 898564 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": 477869, "vin": [ { "gen": { "height": 477859 } } ], "vout": [ { "amount": 16019722996, "target": { "key": "3f864e1d2ad4b402aef66abc2d3e5df66b5ad4464746d3cf5fb0f71ca6a207d7" } } ], "extra": [ 1, 215, 14, 111, 183, 146, 69, 71, 63, 136, 225, 47, 68, 204, 202, 128, 109, 102, 245, 164, 58, 209, 214, 128, 158, 245, 248, 109, 10, 30, 147, 240, 157, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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