Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e3ae322fbced591b38db2e391aa203ed0bf857f0499b17d8cd6a81be2ac0e75

Tx prefix hash: 549469c85916d8a64c8fd6f77b79735afe17a37a17aa8a555570e5ad598f4723
Tx public key: 2be912cb70f5dcc50ff80407d8379e9360b391b253ba3df77d112b22f7363e29
Timestamp: 1712021619 Timestamp [UCT]: 2024-04-02 01:33:39 Age [y:d:h:m:s]: 00:240:09:00:16
Block: 991379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172115 RingCT/type: yes/0
Extra: 012be912cb70f5dcc50ff80407d8379e9360b391b253ba3df77d112b22f7363e290211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 58a59016969b5d45ffc8daff13f4aca1f7b7c005ed960c82cf777c677d061028 0.600000000000 1451713 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": 991389, "vin": [ { "gen": { "height": 991379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "58a59016969b5d45ffc8daff13f4aca1f7b7c005ed960c82cf777c677d061028" } } ], "extra": [ 1, 43, 233, 18, 203, 112, 245, 220, 197, 15, 248, 4, 7, 216, 55, 158, 147, 96, 179, 145, 178, 83, 186, 61, 247, 125, 17, 43, 34, 247, 54, 62, 41, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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