Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779b1f76aa4fb4acbdd2dcfd638ceee598acfdd352faeb0a49e4d95c0af008b1

Tx prefix hash: cad196590b46f1fcf04af7d7544e25bc9e4edbe9b613908bf31cb7adef348938
Tx public key: a49e94c9f493f47fe6bf152349e10f081b3ade65fb6ce8e2a073a8bee15d9c2f
Timestamp: 1682796858 Timestamp [UCT]: 2023-04-29 19:34:18 Age [y:d:h:m:s]: 01:301:11:28:23
Block: 749370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476683 RingCT/type: yes/0
Extra: 01a49e94c9f493f47fe6bf152349e10f081b3ade65fb6ce8e2a073a8bee15d9c2f021100000001faf35c9c000000000000000000

1 output(s) for total of 2.018488669000 dcy

stealth address amount amount idx
00: db32a1145bc51ef2e08cdf6a0a244fdfd4c1bc4655b6c3001cc2d2eb7f4b7487 2.018488669000 1197325 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": 749380, "vin": [ { "gen": { "height": 749370 } } ], "vout": [ { "amount": 2018488669, "target": { "key": "db32a1145bc51ef2e08cdf6a0a244fdfd4c1bc4655b6c3001cc2d2eb7f4b7487" } } ], "extra": [ 1, 164, 158, 148, 201, 244, 147, 244, 127, 230, 191, 21, 35, 73, 225, 15, 8, 27, 58, 222, 101, 251, 108, 232, 226, 160, 115, 168, 190, 225, 93, 156, 47, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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