Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70c1490c828a123cd19db143b2522d7f2b12cc1f91b20fb947d75249b279534e

Tx prefix hash: 2bac89a3ae2e1761f5e5aff21182a6ffbb2489ddfa37bc3046ebf3c0c3ddc2ff
Tx public key: f24f27ea6b60e64d38af07bddd0a89d7220d0f5ed775eebde741dfb7f4189dad
Timestamp: 1581970824 Timestamp [UCT]: 2020-02-17 20:20:24 Age [y:d:h:m:s]: 04:286:16:25:58
Block: 67027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097255 RingCT/type: yes/0
Extra: 01f24f27ea6b60e64d38af07bddd0a89d7220d0f5ed775eebde741dfb7f4189dad0211000000014ac5aa02000000000000000000

1 output(s) for total of 368.054839689000 dcy

stealth address amount amount idx
00: 8f64dfb4fb2de7cb8e5ae896199799c6f38e6b05c150fd9fad126a272605c875 368.054839689000 123447 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": 67037, "vin": [ { "gen": { "height": 67027 } } ], "vout": [ { "amount": 368054839689, "target": { "key": "8f64dfb4fb2de7cb8e5ae896199799c6f38e6b05c150fd9fad126a272605c875" } } ], "extra": [ 1, 242, 79, 39, 234, 107, 96, 230, 77, 56, 175, 7, 189, 221, 10, 137, 215, 34, 13, 15, 94, 215, 117, 238, 189, 231, 65, 223, 183, 244, 24, 157, 173, 2, 17, 0, 0, 0, 1, 74, 197, 170, 2, 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