Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed105f8dd606d64037affe732c9c1c312cb5477e61dc73d8c435e5d467ce2d78

Tx prefix hash: 2d90356ddb0b645fac21dfc090499afaa1eea6e17b783caae82a939c6cb729fd
Tx public key: 3af4bf1379ad2e20efbaad729b1f4d255c61269f626fd52750f7191f99dbce0a
Timestamp: 1717291994 Timestamp [UCT]: 2024-06-02 01:33:14 Age [y:d:h:m:s]: 00:272:00:49:56
Block: 1035109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194379 RingCT/type: yes/0
Extra: 013af4bf1379ad2e20efbaad729b1f4d255c61269f626fd52750f7191f99dbce0a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5247e2012d0a26322a7862526e7a4f9722f3b8f0f5d60cfb2ddf25c62c8760a 0.600000000000 1503628 of 15

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": 1035119, "vin": [ { "gen": { "height": 1035109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5247e2012d0a26322a7862526e7a4f9722f3b8f0f5d60cfb2ddf25c62c8760a" } } ], "extra": [ 1, 58, 244, 191, 19, 121, 173, 46, 32, 239, 186, 173, 114, 155, 31, 77, 37, 92, 97, 38, 159, 98, 111, 213, 39, 80, 247, 25, 31, 153, 219, 206, 10, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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