Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdaff34a99d839d1554e0c4bf5b1c69a07b9c14ff4a9ff3d2f4a5d0317e5920a

Tx prefix hash: 030d53ebaa75f45daae3c9b8689c0ad3e38b1fcf9103aa475fd8d67bea726dfa
Tx public key: 77770bd107c68f1c8015bb892393117b2649fc89f667c833e6c19beff05ae2a6
Timestamp: 1583639949 Timestamp [UCT]: 2020-03-08 03:59:09 Age [y:d:h:m:s]: 04:335:05:56:37
Block: 78545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134017 RingCT/type: yes/0
Extra: 0177770bd107c68f1c8015bb892393117b2649fc89f667c833e6c19beff05ae2a6021100000014e89b4e54000000000000000000

1 output(s) for total of 337.092120853000 dcy

stealth address amount amount idx
00: eda1ecf12085f9a4ff509419cb16e3eb336b440599e62930e6f0c45bd9fb7bfc 337.092120853000 144007 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": 78555, "vin": [ { "gen": { "height": 78545 } } ], "vout": [ { "amount": 337092120853, "target": { "key": "eda1ecf12085f9a4ff509419cb16e3eb336b440599e62930e6f0c45bd9fb7bfc" } } ], "extra": [ 1, 119, 119, 11, 209, 7, 198, 143, 28, 128, 21, 187, 137, 35, 147, 17, 123, 38, 73, 252, 137, 246, 103, 200, 51, 230, 193, 155, 239, 240, 90, 226, 166, 2, 17, 0, 0, 0, 20, 232, 155, 78, 84, 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