Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb29b5279cd330be9700126680d6cd686adf4f231c5cf5fb793a6a7f6dfdf8dd

Tx prefix hash: f208551e290562fb55fce714793eb9a0a402d1b55315d8f9d88a8b7d2346e8e7
Tx public key: d5366c96ec9b5822667ed9499dfaa6df34e397cef9d0d7408b29a870555ac062
Timestamp: 1676213894 Timestamp [UCT]: 2023-02-12 14:58:14 Age [y:d:h:m:s]: 02:057:03:35:22
Block: 695444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562434 RingCT/type: yes/0
Extra: 01d5366c96ec9b5822667ed9499dfaa6df34e397cef9d0d7408b29a870555ac0620211000000015029cbac000000000000000000

1 output(s) for total of 3.045827163000 dcy

stealth address amount amount idx
00: be8f42b664eddb1f379351785d5cb1143f4fd503b6b27d8cb5f25b6e89c10834 3.045827163000 1138399 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": 695454, "vin": [ { "gen": { "height": 695444 } } ], "vout": [ { "amount": 3045827163, "target": { "key": "be8f42b664eddb1f379351785d5cb1143f4fd503b6b27d8cb5f25b6e89c10834" } } ], "extra": [ 1, 213, 54, 108, 150, 236, 155, 88, 34, 102, 126, 217, 73, 157, 250, 166, 223, 52, 227, 151, 206, 249, 208, 215, 64, 139, 41, 168, 112, 85, 90, 192, 98, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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