Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84cb27333b86b71b425adb23c0f21a0b2e2d624424ca1f74e8d18517a8499d99

Tx prefix hash: e21fdcd2643fa40a107a2ea4986ffe38434c918e74222f2d24640c2ea479bfd1
Tx public key: d88046c074f26def7b71e3c3d623803320c1a771d4777c48b2091f890e6bf09a
Timestamp: 1734824537 Timestamp [UCT]: 2024-12-21 23:42:17 Age [y:d:h:m:s]: 00:178:00:56:46
Block: 1180376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126925 RingCT/type: yes/0
Extra: 01d88046c074f26def7b71e3c3d623803320c1a771d4777c48b2091f890e6bf09a021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efc12b82779f4d27924b2481859e3a9392817a21c1ba34b76f492da4fcc7de35 0.600000000000 1666787 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": 1180386, "vin": [ { "gen": { "height": 1180376 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efc12b82779f4d27924b2481859e3a9392817a21c1ba34b76f492da4fcc7de35" } } ], "extra": [ 1, 216, 128, 70, 192, 116, 242, 109, 239, 123, 113, 227, 195, 214, 35, 128, 51, 32, 193, 167, 113, 212, 119, 124, 72, 178, 9, 31, 137, 14, 107, 240, 154, 2, 17, 0, 0, 0, 7, 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