Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f10e014ee7db4becc29e8b1a65404e89abe8019fcc60b7bd8bda7a66e49bd68

Tx prefix hash: cb85245142cced818060fcda9e9342839d990802ec2b8fa39b6f58cb4b7a6802
Tx public key: adf5121d5a50f84e0da3eda766af1edab0a04ff0a31488f2041116e25c6562d4
Timestamp: 1633142150 Timestamp [UCT]: 2021-10-02 02:35:50 Age [y:d:h:m:s]: 03:207:16:18:23
Block: 344877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 925186 RingCT/type: yes/0
Extra: 01adf5121d5a50f84e0da3eda766af1edab0a04ff0a31488f2041116e25c6562d402110000001af60c5d7e000000000000000000

1 output(s) for total of 44.185498730000 dcy

stealth address amount amount idx
00: 7f6bfc50c10124fa633020fa87917694a4addc897bd7cf7dd6296e00dc75f87d 44.185498730000 707517 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": 344887, "vin": [ { "gen": { "height": 344877 } } ], "vout": [ { "amount": 44185498730, "target": { "key": "7f6bfc50c10124fa633020fa87917694a4addc897bd7cf7dd6296e00dc75f87d" } } ], "extra": [ 1, 173, 245, 18, 29, 90, 80, 248, 78, 13, 163, 237, 167, 102, 175, 30, 218, 176, 160, 79, 240, 163, 20, 136, 242, 4, 17, 22, 226, 92, 101, 98, 212, 2, 17, 0, 0, 0, 26, 246, 12, 93, 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