Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fbb61a7d197dd611f315ad27804599fe2f773a99c4650d94d5cbf1abf6dce73

Tx prefix hash: e543083ca8be7ffb511fd18b1bd89f55cf374a98b0afaba90c2502d9810e55f9
Tx public key: c3129cec5e513b30568286a822c0a0aa5778d0f41c5e48b6f8939cc273d5a3f2
Timestamp: 1581237434 Timestamp [UCT]: 2020-02-09 08:37:14 Age [y:d:h:m:s]: 04:295:15:52:20
Block: 61130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103501 RingCT/type: yes/0
Extra: 01c3129cec5e513b30568286a822c0a0aa5778d0f41c5e48b6f8939cc273d5a3f20211000000028a2ee0d9000000000000000000

1 output(s) for total of 384.992040150000 dcy

stealth address amount amount idx
00: 3a76673062442e5948fed1d06e3a62030f68ffb1ffde94295392dccba0110ad0 384.992040150000 112659 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": 61140, "vin": [ { "gen": { "height": 61130 } } ], "vout": [ { "amount": 384992040150, "target": { "key": "3a76673062442e5948fed1d06e3a62030f68ffb1ffde94295392dccba0110ad0" } } ], "extra": [ 1, 195, 18, 156, 236, 94, 81, 59, 48, 86, 130, 134, 168, 34, 192, 160, 170, 87, 120, 208, 244, 28, 94, 72, 182, 248, 147, 156, 194, 115, 213, 163, 242, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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