Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbea47e0e076b6bcbe7874de409c941310939f99d692110a2eecdc5037826776

Tx prefix hash: 1f673054384e28191e579063b39d89ed9804fb076d52024277559c95bd286758
Tx public key: 9571c3d8d17e23d01b1fdc993b2e53e4c7cb827d0d7111b23786f5b971b2520b
Timestamp: 1577932349 Timestamp [UCT]: 2020-01-02 02:32:29 Age [y:d:h:m:s]: 05:035:18:26:37
Block: 36847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175330 RingCT/type: yes/0
Extra: 019571c3d8d17e23d01b1fdc993b2e53e4c7cb827d0d7111b23786f5b971b2520b021100000009d81c26c0000000000000000000

1 output(s) for total of 463.352430388000 dcy

stealth address amount amount idx
00: 12790fa8a2bf2137dd707d77d63ffee29c20d8f9766809b4be67e37e1b0731a1 463.352430388000 62459 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": 36857, "vin": [ { "gen": { "height": 36847 } } ], "vout": [ { "amount": 463352430388, "target": { "key": "12790fa8a2bf2137dd707d77d63ffee29c20d8f9766809b4be67e37e1b0731a1" } } ], "extra": [ 1, 149, 113, 195, 216, 209, 126, 35, 208, 27, 31, 220, 153, 59, 46, 83, 228, 199, 203, 130, 125, 13, 113, 17, 178, 55, 134, 245, 185, 113, 178, 82, 11, 2, 17, 0, 0, 0, 9, 216, 28, 38, 192, 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