Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f6e7d2da4e248dc16d714de31be49881496a1cf659fd65968cfc81c8bfbcc58

Tx prefix hash: a8e5f8a12bfab70e8aee7d3e7a280110eccfe003609538b9e43f2d2bc310fd32
Tx public key: 49a0871bb09b35cbb32cbe86ed70c8bb35c3e1807652c158c64333d3682d5a6c
Timestamp: 1706282560 Timestamp [UCT]: 2024-01-26 15:22:40 Age [y:d:h:m:s]: 01:135:16:13:58
Block: 943802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358107 RingCT/type: yes/0
Extra: 0149a0871bb09b35cbb32cbe86ed70c8bb35c3e1807652c158c64333d3682d5a6c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0dc53143c22b4254090724cf923d86eec1b08dca1df6f22efbcc6e5d7be6eb7 0.600000000000 1402028 of 15

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": 943812, "vin": [ { "gen": { "height": 943802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0dc53143c22b4254090724cf923d86eec1b08dca1df6f22efbcc6e5d7be6eb7" } } ], "extra": [ 1, 73, 160, 135, 27, 176, 155, 53, 203, 179, 44, 190, 134, 237, 112, 200, 187, 53, 195, 225, 128, 118, 82, 193, 88, 198, 67, 51, 211, 104, 45, 90, 108, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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