Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08edfa3d14e82d082a5d75f566f3566bfde4c317fbc08fdf9a2eb829a24ebef0

Tx prefix hash: 43a3c590f17dc502934e98891cee7ffd7831160ec97e654185bdc4a184e776e4
Tx public key: 920c7f2d3865a3a6a032cd571150544efc530a5a3a87a00ccae7cd1e4793ccf8
Timestamp: 1666202623 Timestamp [UCT]: 2022-10-19 18:03:43 Age [y:d:h:m:s]: 02:163:13:46:09
Block: 612567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 638554 RingCT/type: yes/0
Extra: 01920c7f2d3865a3a6a032cd571150544efc530a5a3a87a00ccae7cd1e4793ccf8021100000012faf35c9c000000000000000000

1 output(s) for total of 5.732067312000 dcy

stealth address amount amount idx
00: 38c327e1b23f6035a0ed3ac8af37d23e5706e7cbfbd60e83e488524c8e951f9b 5.732067312000 1049786 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": 612577, "vin": [ { "gen": { "height": 612567 } } ], "vout": [ { "amount": 5732067312, "target": { "key": "38c327e1b23f6035a0ed3ac8af37d23e5706e7cbfbd60e83e488524c8e951f9b" } } ], "extra": [ 1, 146, 12, 127, 45, 56, 101, 163, 166, 160, 50, 205, 87, 17, 80, 84, 78, 252, 83, 10, 90, 58, 135, 160, 12, 202, 231, 205, 30, 71, 147, 204, 248, 2, 17, 0, 0, 0, 18, 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