Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5868d37b97540ed589e496363f9d7e09a48b6a2d0467bc88bfb1cac2c933d1c

Tx prefix hash: 50ae45093f7013ad685c1c4b08dcc594fdc3aeb63440360eedb9256d4c63d018
Tx public key: e61ea4e8503fdd96ab7c7181ffd71c348d0b4d1a5cc0a7a53e63151f892aa4e2
Timestamp: 1734193890 Timestamp [UCT]: 2024-12-14 16:31:30 Age [y:d:h:m:s]: 00:100:17:05:09
Block: 1175136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71747 RingCT/type: yes/0
Extra: 01e61ea4e8503fdd96ab7c7181ffd71c348d0b4d1a5cc0a7a53e63151f892aa4e2021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9360bd065d054e50addcd36ae20c43940c1f0b92aa1c521e8aea9778ea9e2b0e 0.600000000000 1661373 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": 1175146, "vin": [ { "gen": { "height": 1175136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9360bd065d054e50addcd36ae20c43940c1f0b92aa1c521e8aea9778ea9e2b0e" } } ], "extra": [ 1, 230, 30, 164, 232, 80, 63, 221, 150, 171, 124, 113, 129, 255, 215, 28, 52, 141, 11, 77, 26, 92, 192, 167, 165, 62, 99, 21, 31, 137, 42, 164, 226, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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