Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5510692dd3c2df205363b834eb3a372cf87f363a13d0fba7e32d1f43a268d1bc

Tx prefix hash: f7243441740ca79d33d5f972b6c1cd824fce87f4a89973f8e04f024f77d4bc57
Tx public key: 0dcd0bd1168ab85b8bfb3ef0144ee98a3aa8c521586a099991049e3ac88b88c6
Timestamp: 1682627404 Timestamp [UCT]: 2023-04-27 20:30:04 Age [y:d:h:m:s]: 01:348:01:34:56
Block: 747973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510012 RingCT/type: yes/0
Extra: 010dcd0bd1168ab85b8bfb3ef0144ee98a3aa8c521586a099991049e3ac88b88c60211000000017e406890000000000000000000

1 output(s) for total of 2.040177394000 dcy

stealth address amount amount idx
00: 9c989b6e788261fc2f46852c0e9594d7176e07b002bc96a551f8cf6a25d2be87 2.040177394000 1195748 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": 747983, "vin": [ { "gen": { "height": 747973 } } ], "vout": [ { "amount": 2040177394, "target": { "key": "9c989b6e788261fc2f46852c0e9594d7176e07b002bc96a551f8cf6a25d2be87" } } ], "extra": [ 1, 13, 205, 11, 209, 22, 138, 184, 91, 139, 251, 62, 240, 20, 78, 233, 138, 58, 168, 197, 33, 88, 106, 9, 153, 145, 4, 158, 58, 200, 139, 136, 198, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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